E2B MCP integration for AI agents.
Connect AI agents to E2B through 4 structured actions, including get sandbox, create sandbox, and delete sandbox. Review authentication, inputs, workflows, a…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the E2B integration exposes
The E2B Agent App exposes 4 provider-backed actions for ai and developer tools work. Its current contract lets an authorized agent get one e2b sandbox by sandbox identifier, create an e2b sandbox from a template, and kill an e2b sandbox by sandbox identifier. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected E2B account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real E2B capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_sandboxREADGet one E2B sandbox by sandbox identifier.
INPUTS: sandboxID
create_sandboxWRITECreate an E2B sandbox from a template.
INPUTS: templateID / timeout / autoPause / autoPauseMemory / autoResume
delete_sandboxHIGH IMPACTKill an E2B sandbox by sandbox identifier.
INPUTS: sandboxID
list_sandboxesREADList E2B sandboxes visible to the current API key.
INPUTS: metadata / state / nextToken / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_sandbox
sandboxIDOPTIONAL- The E2B sandbox identifier.
create_sandbox
templateIDREQUIRED- The E2B template identifier used to create the sandbox.
timeoutOPTIONAL- Time to live for the sandbox in seconds.
autoPauseOPTIONAL- Whether E2B should automatically pause the sandbox after timeout.
autoPauseMemoryOPTIONAL- Whether auto-pause should preserve the sandbox memory snapshot when autoPause is true.
autoResumeOPTIONAL- Auto-resume configuration for paused sandboxes.
delete_sandbox
sandboxIDOPTIONAL- The E2B sandbox identifier.
list_sandboxes
metadataOPTIONAL- Metadata query used to filter sandboxes, such as "user=abc&app=prod". Keys and values must already be URL encoded.
stateOPTIONAL- Sandbox states used to filter the list.
nextTokenOPTIONAL- Cursor returned by E2B for the next page.
limitOPTIONAL- Maximum number of sandboxes to return per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Sandbox
Get one E2B sandbox by sandbox identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_sandboxControl Create Sandbox
Create an E2B sandbox from a template. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_sandboxVerify with List Sandboxes
List E2B sandboxes visible to the current API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_sandboxesSAFETY BOUNDARY
Operate E2B with explicit limits
- Authorize E2B with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_sandbox` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in E2B rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the E2B task completed successfully.
CONNECTION MODEL
API key
E2B API key used with the X-API-Key header. Create or view keys in the E2B dashboard: https://e2b.dev/dashboard?tab=keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by E2B.