E2b
Spin up isolated E2B sandboxes from Claude Code or Cursor so agent-generated code runs safely without touching your laptop.
Overview
com.mcparmory/e2b is a MCP server for the Build phase that creates and manages secure E2B sandboxes so AI agents can run code in isolation.
What is this MCP server?
- Create and tear down secure E2B sandboxes for AI agent code over MCP stdio
- Ship as PyPI uvx package mcparmory-e2b or OCI image ghcr.io/mcparmory/e2b:1.0.5
- stdio transport for Claude Code, Cursor, Codex, and Windsurf MCP clients
- Isolates arbitrary agent-written scripts from host filesystem and secrets
- Registry entry com.mcparmory/e2b at version 1.0.5 on mcparmory/registry
- Server version 1.0.5 in MCP schema 2025-12-11
- 2 distribution packages: PyPI uvx and OCI Docker on ghcr.io/mcparmory/e2b:1.0.5
- stdio transport on both packages
Community signal: 25 GitHub stars.
What problem does it solve?
Letting agents execute untrusted code on your dev machine risks data loss, leaked secrets, and inconsistent environments.
Who is it for?
Indie builders prototyping code-execution agents, eval harnesses, or auto-fix loops that need a real runtime without local Docker sprawl.
Skip if: Teams that only need static analysis, or production workloads that should run on your own Kubernetes instead of ephemeral sandboxes.
What do I get? / Deliverables
Your agent can provision E2B sandboxes via MCP and run generated code in a controlled remote environment with predictable teardown.
- Registered MCP server entry pointing at com.mcparmory/e2b
- Agent-callable sandbox create and manage workflow against E2B
- Repeatable local or containerized stdio transport via uvx or Docker
Recommended MCP Servers
Journey fit
Sandbox execution is part of wiring and hardening the agent layer while you are still building integrations, not a launch or growth task. agent-tooling is the shelf for MCP bridges that provision runtimes and tools agents call during development.
How it compares
MCP integration to E2B sandboxes, not an agent skill that writes application code for you.
Common Questions / FAQ
Who is com.mcparmory/e2b for?
Solo and small-team builders using Claude Code or similar agents who want E2B isolated execution wired through the Model Context Protocol.
When should I use com.mcparmory/e2b?
Use it during Build when an agent needs to run, test, or iterate on code in a sandbox rather than on your host OS.
How do I add com.mcparmory/e2b to my agent?
Add the MCP server to your client config with stdio transport, using runtimeHint uvx for mcparmory-e2b on PyPI or docker for ghcr.io/mcparmory/e2b:1.0.5, and set your E2B API key in the environment.