How to Use the E2B MCP in Claude

Q: How do I configure the E2B MCP server in Claude Desktop?

Open your local claudedesktopconfig.json file and add the server definition under the mcpServers block. Provide your API key as an environment variable, then restart the app to see the tools.

Run untrusted code instantly inside secure Firecracker VMs directly from your Claude Desktop chat window.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect E2B MCP to Claude Desktop

Create your Vinkius account to connect E2B to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup E2B with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Spin up isolated microVMs in Claude Desktop

`create_sandbox` spins up a secure Firecracker microVM directly from your Claude Desktop chat window in 150 milliseconds. Your chat agent runs Python or Node templates to test snippets locally without risking your main operating system. The local chat interface handles the execution results instantly. If Claude Desktop leaves a task hanging, the 300-second timeout automatically stops the VM to keep your machine fast.

Clean up active environments on demand

Run `kill_sandbox` to instantly destroy the active VM and delete its files from your Claude Desktop session. This tool ensures that untrusted code tested in your chat does not leave active background processes running on your computer. You control the VM lifecycle with simple chat commands. Deleting the sandbox leaves your Claude Desktop environment clean and ready for the next prompt.

Monitor active sandboxes from your chat input

Use `list_sandboxes` to check which active VMs are running under your Claude Desktop configuration. The desktop app displays these environments so you can track resource consumption easily. This MCP Server keeps your local chat sessions organized. You will always see active runtimes before starting a new execution block.

Setup guide

Set up E2B MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The E2B MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the E2B MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under e2b-mcp.

json

{
  "mcpServers": {
    "e2b-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by E2B. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect E2B now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about E2B MCP in Claude Desktop

Open your local `claude_desktop_config.json` file and add the server definition under the `mcpServers` block. Provide your API key as an environment variable, then restart the app to see the tools.

Yes, your agent can specify Python, Node, or base templates when calling `create_sandbox`. This allows Claude Desktop to run diverse codebases in isolated environments.

The system enforces a default 300-second limit on each VM. If Claude Desktop leaves a sandbox running, E2B automatically terminates it to prevent resource leaks.

E2B uses Firecracker microVMs that boot in 150ms, bypassing the slow startup of traditional container tools. Claude Desktop calls the MCP server to get immediate execution feedback.

Your temporary files, executed code, and environment variables are confined to a single-use Firecracker VM. E2B isolates memory at the hardware level, and once the timeout hits, the entire filesystem is permanently shredded.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript