Skip to main content
Autodock allows you to spawn, connect to, and manage remote development servers by talking to your favorite agents using MCP.
Mike’s tip: When I use Autodock at Rightware, I start a server using MCP and leave it up during the day so that folks can test out features end-to-end as I hack on them in real time.

Quickstart

Add the Autodock MCP server to your favorite AI tool:
Mike’s tip: This always trips me up. Once in your agent, you usually need to type /mcp, find Autodock, and authorize it. After that, it’s smooth sailing.
After installing Autodock, try the following commands with your agent:
  1. Please spin up an autodock box.
  2. Sync my work.
  3. Run everything.
  4. Expose ports.
That should get you up and running! For more advanced use cases, see the reference below.

Tool Reference

Environment Lifecycle

File & Command Operations

Port Exposure

Reserved Instances

Reserved instances run 24/7 without auto-stopping and don’t count against your concurrent environment limit. A reserved instance costs $149 and lasts for 30 days. Requires a paid plan (Starter or Pro).

Inbound Email

Receive emails at *@{slug}.autodock.io for testing auth flows, notifications, and more.

GitHub Actions Runner

Autodock environments include a pre-installed GitHub Actions runner at /opt/actions-runner.
The runner is configured in ephemeral mode - it processes one job and then exits. Labels autodock and your environment slug are automatically added.

Account & API Keys