How to use E2B with VS Code
You want E2B inside VS 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 VS 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 VS Code
-
Add the server
VS Code 1.107.0 or higher. Command Palette → MCP: Add Server… → choose HTTP, paste your gateway URL, and name it something like mcp-arcade.
-
Start it and authenticate
Click Start next to the server in mcp.json or under Extensions → MCP Servers - Installed, then approve the Arcade sign-in and consent screens.
-
Try it out
Open the chat pane, switch to Agent mode, and ask it to use one of your E2B tools.
Full VS Code guide in the docs steps verified 2026-08-13
Try these E2B prompts
VS 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.