27 tools from the Autodock MCP Server, categorised by risk level.
View the Autodock policy →account.info Return information about the currently authenticated Autodock user account.list_api_keys List your API keys (shows prefix only, not full key) browser.poll Retrieve captured browser events from a listener session.
Returns console logs, network requests, and errors captured from the browser.
Also retur... 2/5 browser.shot Request a screenshot from the browser.
The screenshot will be captured asynchronously by the browser.
IMPORTANT: Screenshots can take 10-15 second... 2/5 browser.stop Stop a browser listener session.
This will signal the browser to stop capturing and clean up server resources.
The user can also stop from the bro... env.extend Extend the auto-stop timer for a running environment. Resets the idle timer and sets a new auto-stop duration. env.launch Launch a new Autodock environment. Typically takes 1-2 minutes. env.list List environments for the authenticated user env.listExposed List exposed ports for an environment env.observe Get Loki query commands for observing logs on an Autodock environment.
Returns SSH+curl commands for querying the local Loki instance. Does NOT fe... 2/5 env.reserve Preview the cost of reserving an environment for 30 days ($149). Reserved environments do not auto-stop and do not count against your concurrent en... env.reserve_confirm Confirm reservation and process $149 payment. Environment will not auto-stop for 30 days after reservation. Payment is charged immediately to your ... env.save Get templates for saving session setup to AUTODOCK.md.
Returns environment details, exposed ports, and command templates for documentation.
If en... env.status Fetch a specific environment by ID account.create_api_key Create a new API key for headless MCP authentication.
The key will be shown ONCE - make sure to save it securely.
Use the key with: claude mcp add... 2/5 env.get_ssh_key Fetch a fresh download URL for the SSH private key. Use this if the key was corrupted during initial save (e.g., "error in libcrypto" when running ... 2/5 env.sync REQUIRED before syncing files to an Autodock environment.
Provides SSH connection details and rsync templates. Does NOT perform the sync itself.
I... 2/5 browser.listen Start a browser listener to capture console logs, network requests, and errors from the user's browser.
After starting, provide the user with the ... 4/5 env.email Documentation for receiving emails in an Autodock environment.
Each environment can receive emails at *@{slug}.autodock.io. Emails are delivered v... 3/5 env.expose Expose a port on an environment with a public HTTPS URL.
Creates https://<name|port>--<slug>.<base-domain>. Returns URL and .env update guidance.
... 3/5 env.gh_runner Documentation for configuring and running a GitHub Actions self-hosted runner.
The GitHub Actions runner is pre-installed at /opt/actions-runner. ... 5/5 env.restart Restart a stopped environment. Boots the same instance with preserved storage. 3/5 env.run REQUIRED before executing commands on an Autodock environment.
ALWAYS call this tool before using SSH to run commands - it provides:
• SSH key pat... 4/5 env.stop Stop (power down) an environment. Safe to restart later. 3/5 The Autodock MCP server exposes 27 tools across 4 categories: Read, Write, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Autodock server.
Autodock tools are categorised as Read (14), Write (3), Destructive (3), Execute (7). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept