Claude Code How to use E2B with Claude Code
You want E2B inside Claude Code so it can run reproducible data analyses, generate charts from raw data, test code in an isolated environment, and validate generated code before deployment — without you copy-pasting between tabs. Here is the whole setup, once.
Create your E2B gateway
The gateway is the thing Claude Code connects to, and it is where you decide which E2B tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your E2B tools
In the dashboard, create a gateway and pick the E2B tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Claude Code
-
Add the gateway as a remote HTTP MCP server
claude mcp add arcade --transport http "<YOUR_ARCADE_GATEWAY_URL>"
-
Verify it was added
claude mcp get arcade claude mcp list
-
Try it out
Open Claude Code in your project and ask it to use one of your E2B tools.
Full Claude Code guide in the docs steps verified 2026-08-13
Try these E2B prompts
Claude Code can now act on your E2B account. Click a prompt to copy it.
Treat sandbox execution as arbitrary code: use tool permissions to limit which workflows can run code or generate charts. Pair it with Contextual Access policies so an agent can run only the actions approved for its context.
