Shipyard Cli MCP Server

Shipyard Cli MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A tool to manage Ephemeral Environments on the Shipyard platform.

What the assistant can call

Once Shipyard Cli is connected, these are the calls the assistant has available:

• get_environments — List environments with filtering
• get_environment — Get specific environment details
• stop_environment — Stop a running environment
• restart_environment — Restart a stopped environment
• rebuild_environment — Rebuild with latest commit
• cancel_environment — Cancel environment's latest build
• revive_environment — Revive a deleted environment
• get_services — List services in an environment
• get_logs — Get logs from a service
• get_volumes — List volumes in an environment
• reset_volume — Reset volume to initial state
• get_snapshots — List volume snapshots

Configuration and credentials

You will need one environment variable: SHIPYARD_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Shipyard Cli's toolset — get_environments, get_environment, stop_environment and 11 more — is a fair guide to whether it matches your workflow. It is maintained by shipyard; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Shipyard Cli's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Shipyard Cli.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the shipyard cli mcp server does with a few real requests.