MCP Servers

Crafting provides a centrally managed mechanism to advertise MCP (Model Context Protocol) servers to all sandboxes in an org. Rather than configuring MCP servers in each sandbox individually, they can be registered once at the org level and automatically become available everywhere.

Adding an MCP Server

To make an MCP server globally available to all sandboxes in the org:

  1. Create a Pinned sandbox running the MCP server, ensuring:
  2. The listening port is exposed as an INTERNAL endpoint with auth_proxy disabled. (See Endpoints.)

  3. The sandbox definition includes the MCP server declaration:

    yaml customizations: - mcp_server: endpoint: ENDPOINT-NAME

    Where ENDPOINT-NAME is the name of the internal endpoint exposing the MCP server.

  4. Authorize the MCP server as an org admin:

  5. Visit Connect / LLM in the Web Console.
  6. Go to the Discovery tab.
  7. Authorize the MCP server sandbox.

Using MCP Servers

Once authorized, the MCP configuration is available in all workspaces:

File Contents
/run/sandbox/fs/metadata/mcp.json MCP configuration for all authorized org-level MCP servers
/opt/sandboxd/etc/mcp.json MCP configuration for Crafting-specific tools

These configuration files can be loaded by any agent or MCP-compatible client running inside the workspace.

For the built-in coding CLI commands (cs claude, cs gemini, cs codex), both MCP configuration files are loaded automatically. No additional setup is required.

See Also