How to connect E2b to OpenClaw
Connect E2b to OpenClaw with ClawLink: paste your E2b key once and 27 tools work from chat. No MCP server to run, nothing stored on your machine.
E2bAPI KEYMCPOpen-source Code Interpreting for AI Apps.. Once connected, OpenClaw can read and act on E2b from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to E2b access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical E2b setup: install one ClawHub skill, connect E2b in the browser, and OpenClaw can call real E2b actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to E2b.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect E2b
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with E2b?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect E2b in the ClawLink dashboard — paste your E2b API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from E2b, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once E2b is connected in the dashboard, that agent calls the same 27 E2b tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
E2b MCP for OpenClaw
Looking for a E2b MCP server for OpenClaw? ClawLink connects E2b to OpenClaw and exposes 27 E2b tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes E2b integration works the same way.
What the OpenClaw E2b integration can do
27 E2b tools are ready for OpenClaw once the account is connected. The 25 below are the ones people reach for most; your agent can call all 27.
25 of 27 E2b tools for OpenClaw
| Tool | What it does |
|---|---|
Get health e2b_get_health | Check the health status of the E2B API |
Get sandbox e2b_get_sandbox | Retrieve detailed information about a specific sandbox by its ID |
Get sandbox lifecycle events e2b_get_sandbox_lifecycle_events | Retrieve the latest lifecycle events for a particular sandbox instance |
Get sandbox metrics e2b_get_sandbox_metrics | Retrieve timestamped CPU, memory, and disk usage metrics for a sandbox |
Get sandboxes logs e2b_get_sandboxes_logs | Retrieve logs from a specific E2B sandbox instance |
Get teams metrics e2b_get_teams_metrics | Retrieve timestamped CPU, memory, and disk usage metrics for a team |
Get teams metrics max e2b_get_teams_metrics_max | Retrieve the maximum value for a specific team metric in a given interval |
Get templates build status e2b_get_templates_build_status | Get the status of a template build |
Get templates files e2b_get_templates_files | Get an upload link for a tar file containing build layer files |
Get webhook e2b_get_webhook | Retrieve the current webhook configuration for a specific webhook |
List sandboxes e2b_list_sandboxes | List all running and paused sandboxes associated with your team |
List sandboxes metrics e2b_list_sandboxes_metrics | Retrieve timestamped CPU, memory, and disk usage metrics for multiple sandboxes |
List team sandbox lifecycle events e2b_list_team_sandbox_lifecycle_events | Retrieve the latest lifecycle events across all sandboxes associated with the team |
List templates e2b_list_templates | List all available E2B templates for your team |
List webhooks e2b_list_webhooks | Retrieve all registered webhooks for your team |
Connect sandbox e2b_connect_sandbox | Connect to an existing E2B sandbox and retrieve its details |
Create template e2b_create_template | Create a new E2B template with specified configuration |
Create webhook e2b_create_webhook | Register a new webhook to receive sandbox lifecycle events for the team |
Pause sandbox e2b_pause_sandbox | Pause a running E2B sandbox preserving its filesystem and memory state |
Post sandboxes e2b_post_sandboxes | Create a new E2B sandbox from a template |
Post sandboxes timeout e2b_post_sandboxes_timeout | Set the timeout for an E2B sandbox |
Refresh sandbox e2b_refresh_sandbox | Refresh an E2B sandbox and extend its time to live |
Start template build e2b_start_template_build | Start a build for an E2B template |
Update template e2b_update_template | Update an E2B template configuration |
Update webhook e2b_update_webhook | Update an existing webhook configuration including URL, enabled status, and subscribed events |
Try it: find the E2b tool you need
Browse the 25 E2b tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from E2b, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from E2b, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from E2b, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from E2b, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want E2b working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the E2b API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected E2b account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for E2b. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right E2b actions to the runtime in a format your agent can reliably use. | 27 tools for E2b are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes E2b to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect E2b in the browser, and the 27 tools above work from chat. There is no SDK and no config file, and the E2b key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the E2b skill but can't call the tools
The ClawHub skill teaches OpenClaw about E2b, but the calls run through the ClawLink plugin and your connected account. Make sure E2b is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect E2b from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling E2b tools
E2b tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every E2b call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
E2b returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for E2b has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw E2b integration?
Yes. ClawLink is the fastest way to connect OpenClaw to E2b: link your E2b account once in the browser and OpenClaw can call the E2b API through 27 ready-made tools — no custom code or token handling.
How do I add E2b to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink E2b skill from ClawHub, then you click Connect in the dashboard to authorize E2b. OpenClaw calls the tools from the next message — no config files, and the E2b key you paste is stored server-side instead of in your environment.
How long does it take to connect E2b to OpenClaw?
About two minutes. Sign in, click Connect next to E2b in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring E2b up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want E2b working from chat.
OpenClaw installed the E2b skill but can't call the tools
The ClawHub skill teaches OpenClaw about E2b, but the calls run through the ClawLink plugin and your connected account. Make sure E2b is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw GitHub integration
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
SafetyCulture tools
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.