Application Development
E2B MCP connector
The E2B connector brings your E2B sandboxes, snapshots and templates to Claude, ChatGPT, Cursor and any MCP client, so your team can create, pause, resume and inspect sandboxes by asking in plain language, with every action logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
64 tools
How to connect
How to connect E2B to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect E2B once
-
Open Connections, choose Add connection, and pick E2B.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an E2B API key. One person generates a token in E2B and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect E2B to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect E2B to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect E2B to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect E2B to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with E2B through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Spin up a sandbox for a quick test
Ask for a fresh E2B sandbox from a named template, run the check you need, then shut it down when you are done. No console visits in between.
-
Platform
Find and pause idle sandboxes
List every running E2B sandbox, spot the ones nobody has touched today, and pause them in one go before they eat the budget.
-
DevOps
Pull logs and metrics after a failure
When a job in a sandbox dies, ask for its logs and recent metrics and get the answer in the same chat where you are debugging.
-
Engineering
Snapshot a sandbox before a risky change
Take a snapshot of an E2B sandbox before you upgrade a dependency or rewrite a script, so there is a known good state to come back to.
-
Platform
Keep templates current and rebuilt
Update an E2B template, start its build, and confirm it finished, all without leaving the tool where the change was discussed.
-
Data
Extend a long-running analysis
When a data run in an E2B sandbox needs more time, ask to refresh it or set a longer timeout instead of losing the work.
Try asking
- “List every running E2B sandbox and its timeout.”
- “Show logs for the sandbox that failed last night.”
- “Snapshot the long running sandboxes on the agents team.”
AI tools
E2B tools for your AI agents
64 tools are ready to call through Elaichi's MCP endpoint the moment you connect E2B, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting E2B gets you
6 screens from the product, each doing one job for your E2B account.
The agent
Ask about E2B sandboxes in plain language.
Starter prompts read live sandboxes, snapshots and metrics, then answer in a sentence.
- sandboxes
- snapshots
- logs
- metrics
Ask Elaichi to work across your apps.
List every running E2B sandbox and its timeout.
Show logs for the sandbox that failed last night.
Snapshot the long running sandboxes on the agents team.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Every client reaches E2B over OAuth through one org endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
64 E2B tools are ready to call.
Create, pause, resume and snapshot sandboxes, read logs and metrics, no custom code.
- List all E2B sandboxes
- Create a E2B sandbox
- Get single E2B sandbox by ID
- Delete a E2B sandbox by ID
ElaichiToolsToolboxes
Each team gets its own E2B toolbox.
Platform, agents and support teams see only the sandbox tools their work needs.
- Platform
- Agents
- Data Science
- Support
ElaichiToolboxesShared connections
Teammates run sandboxes without touching a key.
See who connected each E2B account and how many teams and members share it.
- Platform Prod
- Platform Staging
- Agents Team
- Data Science
ElaichiConnectionsAudit log
Every sandbox call is written down.
When, who, what happened, type and resource for each E2B action taken.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest ships.
Six steps fetch E2B sandboxes, group them, draft a digest, get approval, post back.
E2B digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch sandboxes
E2B
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
E2B
Queued
Collections and dashboards
Sandbox health arrives before anyone asks.
Four metrics, fourteen days of sandboxes created and a team breakdown, refreshed on schedule.
E2B health
Refreshed 4 minutes ago · every 15 minutes · from the sandboxes collection
Sandboxes
1,284 ↓ 12%
Snapshots
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Sandboxes created
Last 14 days
By team
Share of activity
Platform Prod 34%
Platform Staging 27%
Agents Team 21%
Data Science 18%
FAQ
Frequently asked questions
How do I connect E2B to Claude?
Two steps. In Elaichi, choose E2B from the connector catalog and paste in an API key from your E2B dashboard; there is no OAuth app to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and E2B is ready to use.
Does E2B work with ChatGPT and Cursor as well as Claude?
Yes. Once E2B is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect E2B once and every client picks it up.
What can an AI agent actually do with my E2B account?
Through the E2B connector an agent can list your sandboxes, create new ones from a template, pause, resume, refresh or delete them, change their timeout, pull their logs and metrics, and take snapshots. It can also list, create, update, rebuild and delete templates. Because E2B has many available actions, short concrete asks such as "pause every sandbox older than an hour" work better than long paragraphs.
Does connecting E2B give the AI access to my whole E2B team?
Access follows the API key you connect, so the agent can only reach the E2B sandboxes and templates that key can already see. Elaichi can narrow that further, for example allowing reads but not deletes, and it never widens what E2B itself allows.
Can I stop an agent from deleting or changing things in E2B?
Yes. Restrictions in Elaichi work per action, so you can allow listing E2B sandboxes and reading logs while blocking deletes, template rebuilds or bulk changes. A blocked action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to an E2B connection when someone leaves?
Offboarding a person in Elaichi ends their access to E2B through every client at once. A shared E2B connection keeps working for everyone else on the team. If you want to remove E2B entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor and every other client together.
Put E2B in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.