Skip to main content
An MCP Box serves MCP tools to your agent. Each tool reads or changes an API Box, so the agent works on the same state as calls to that API Box.

​
Snapshots

An MCP Box Snapshot holds the tools of one MCP server and names the API Box Snapshot it was built against. You cannot build one through the API: Continuous publishes MCP Box Snapshots into your workspace on request. GET /v1/mcpbox-snapshots lists them.

​
Create and connect

POST /v1/mcpbox takes a snapshot_id and an apibox_id. The API Box must have started from the API Box Snapshot that the MCP Box Snapshot was built against. The response returns the MCP Box in starting, with its endpoint and token. Read it until it is running. Send MCP requests over Streamable HTTP to the endpoint followed by /mcp, with the token in this header:
GET /v1/mcpbox/{id}/connection returns the endpoint and token again. The MCP Box keeps no state of its own. While its API Box is stopped, each tool call returns the API Box’s refusal as a tool error.

​
Stop, start and delete

POST /v1/mcpbox/{id}/stop releases the MCP Box’s runtime; its API Box keeps running. POST /v1/mcpbox/{id}/start starts it again with the same token. DELETE /v1/mcpbox/{id} removes it; its API Box stays.