# How to connect E2b to Hermes Agent (paste one key, 27 tools) > Connect E2b to Hermes with ClawLink: paste your E2b key once and 27 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/e2b Most guides for giving Hermes Agent E2b access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical E2b setup: pair once in the browser and your always-on Hermes agent can act on E2b for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to E2b. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect E2b** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect e2b # connect E2b (browser OAuth) npx -y @useclawlink/cli actions e2b # list available actions npx -y @useclawlink/cli run e2b --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect E2b in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your E2b API key once. Verify the connection by asking Hermes: > Pull the relevant data from E2b, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## E2b MCP for Hermes Looking for a E2b MCP server for Hermes Agent? ClawLink connects E2b to Hermes Agent and exposes 27 E2b tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw E2b integration](https://claw-link.dev/openclaw/e2b) works the same way. ## What the Hermes Agent E2b integration can do 27 E2b tools are ready for Hermes Agent 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 Hermes | 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 | ## Example prompts **Get Health** > Pull the relevant data from E2b, summarize it in plain English, and point out anything that needs attention. **Get Sandbox** > Pull the relevant data from E2b, summarize it in plain English, and point out anything that needs attention. **Get Sandbox Lifecycle Events** > Pull the relevant data from E2b, summarize it in plain English, and point out anything that needs attention. **Get Sandbox Metrics** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use E2b Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent E2b integration? Yes. ClawLink is the fastest way to connect Hermes to E2b: link your E2b account once in the browser and Hermes Agent can call the E2b API through 27 ready-made tools — no custom code or token handling. ### How do I connect E2b to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect E2b in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to E2b in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want E2b working from chat. ### Hermes paired but still can't use E2b Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/hermes/safetyculture) — 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.