Skip to main content
Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.

Connect to the MCP server

The MCP server operates through streamable HTTP at the sandbox’s base URL:
The base URL of a sandbox can be retrieved via the management API of sandboxes under metadata.url or via the Blaxel SDKs. Connect to this MCP server like any other MCP server through the endpoint shown above. Instructions for some popular applications are provided below.
You must provide your Blaxel API key in the Authorization header. If your user has access to multiple workspaces, include the workspace header as well.
  • Required: Authorization: Bearer <APIKEY>
  • Optional (multi-workspace): X-Blaxel-Workspace: <WORKSPACE_NAME_OR_ID>
Bearer-token authentication only — there is no OAuth for connecting to the sandbox MCP endpoint. See MCP endpoints at a glance for how this compares to the other MCP surfaces on Blaxel.

Add to Cursor

Add the server to ~/.cursor/mcp.json:

Add to Claude Code

Add the remote HTTP server to your Claude Code by running the following command:
Follow this tutorial to build a Claude Agent SDK-powered agent that connects to a Blaxel sandbox and operates it using the sandbox’s MCP server.

Add to Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

Add to Goose

Add to ~/.config/goose/config.yaml:

Tools available in the MCP server

Process management

Filesystem operations

Code search and navigation

Code editing

Using Blaxel SDK, you can retrieve the tools for a sandbox in any supported framework format by passing the sandbox’s name. For example, in LangGraph:
Read more documentation on connecting to the MCP server directly from your code.

Example: Connect to a sandbox from Claude Agent SDK

Connect Claude Code to a Blaxel Sandbox

Build a Claude Agent SDK agent that connects to a Blaxel sandbox and operates it using the sandbox’s MCP server.
Last modified on July 14, 2026