The volume snapshot tools are what make this more than a status reader: load a known state, run the thing that failed, reset, repeat. That loop is the part a person usually spends an afternoon on.
An MCP server built into the Shipyard CLI. It runs as a subcommand over stdio and gives an agent the controls the CLI has: environments, the services inside them, volumes and their snapshots, and the organization all of it belongs to.
- Environments listed with filters, read in detail, stopped, restarted, rebuilt against the latest commit, cancelled mid-build, or revived after deletion
- Services inside an environment listed, and logs pulled from any one of them
- Volumes listed and reset to their initial state
- Volume snapshots listed, created and loaded, so a run can start from a known state
- Organizations listed, and the default one read or changed before anything else runs
- Pairs with a browser-automation server for visual testing against a live Shipyard environment
The Shipyard CLI, installed from the project's Homebrew tap. Add the server to your client as shipyard mcp serve; an API token and organization name go in as environment variables unless the CLI is already configured. Container exec, port forwarding and telepresence stay CLI commands — those tools return the command to run rather than running it.
One command plus a key — curl https://www.shipyard.sh/install.sh | bash, then supply credentials