mcp-server and claude-code-mcp
These are complementary tools that serve different code execution architectures: one enables Claude to run code locally on the user's machine, while the other delegates execution to a remote sandboxed environment, allowing users to choose between local convenience and isolated security.
About mcp-server
e2b-dev/mcp-server
Giving Claude ability to run code with E2B via MCP (Model Context Protocol)
Implements isolated code execution through E2B's sandboxed environment, enabling Claude to run and test code snippets across multiple languages without local system access. Supports both JavaScript and Python implementations with Smithery integration for seamless Claude Desktop installation. Uses the MCP stdio transport protocol to establish real-time communication between Claude and the E2B code interpreter backend.
About claude-code-mcp
KunihiroS/claude-code-mcp
MCP Server connects with claude code local command.
Exposes Claude Code CLI capabilities (explain, review, fix, edit, test code) as MCP tools through stdio-based JSON communication, using Base64 encoding to safely handle special characters in natural language inputs. Implements request routing via `child_process.spawn` to execute templated or custom Claude CLI commands and return results to MCP hosts. Integrates with Claude Desktop and other MCP hosts, supporting Node.js 18+ with configurable logging and environment-based CLI path configuration.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work