get_environmentsLABSCO SUMMARY
Environments an agent can reset, not just read.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Follow the published steps — curl https://www.shipyard.sh/install.sh | bash
USE CASES
01
Getting an environment back to a known state
Load the snapshot you took earlier, or reset the volume outright, before running the test again.
02
Chasing a failure in a preview environment
Find the environment, list the services inside it, and read the logs of the one that is failing.
03
Rebuilding on the latest commit
Rebuild the environment, or cancel the build already running and start it again from the current code.
04
Working across more than one organization
List the organizations and set the default first, so nothing runs against the wrong one.
20 tools
Listed in project docs. Your client may show a different list.
get_environmentstop_environmentrestart_environmentrebuild_environmentcancel_environmentrevive_environmentget_servicesget_logsget_volumesreset_volumeget_snapshotscreate_snapshotload_snapshotget_orgsget_orgset_orgexec_serviceport_forwardtelepresence_connectBEFORE YOU INSTALL
What to know first
Tools you get
20 tools named in the project's documentation. Three tools, exec_service, port_forward and telepresence_connect, only return help text pointing to CLI commands, leaving 17 that act.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
curl https://www.shipyard.sh/install.sh | bash
shipyard login
claude mcp add shipyard --env SHIPYARD_API_TOKEN=<YOUR_SHIPYARD_API_TOKEN> --env SHIPYARD_ORG=<YOUR_SHIPYARD_ORG> -- shipyard mcp serveMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add shipyard --env SHIPYARD_API_TOKEN=<YOUR_SHIPYARD_API_TOKEN> --env SHIPYARD_ORG=<YOUR_SHIPYARD_ORG> -- shipyard mcp serve
