E2B documents an MCP gateway that runs inside cloud sandboxes, exposing 200+ tools from the Docker MCP Catalog (Browserbase, Exa, Notion, Stripe, GitHub, and others) through a unified HTTP endpoint with bearer-token auth. Developers create a Sandbox with an `mcp` configuration map of server credentials, call `getMcpUrl()` / `getMcpToken()`, and attach the gateway to MCP clients such as Claude Code via `claude mcp add --transport http`. Sandboxes provide an internet-connected Linux environment where agents can install packages, run terminal commands, and execute generated code while MCP tools stay type-safe per E2B's overview at e2b.dev/docs/mcp.
Use cases
- Bundle Browserbase, Exa, and Airtable MCP tools for a research agent inside one sandbox session
- Give coding agents a remote Linux runtime plus catalog MCP tools without local Docker sprawl
- Register the sandbox MCP URL with Claude Code for HTTP transport workflows documented by E2B
- Pre-pull custom MCP templates to reduce cold-start latency per E2B custom-template guides
- Attach GitHub-hosted custom MCP servers when catalog entries are insufficient
Key features
- Claude Code
- Cursor
- VS Code
- Codex
Frequently Asked Questions
- Where do MCP servers come from?
- E2B routes through the Docker MCP Catalog by default and documents custom servers from GitHub separately.
- How do clients authenticate?
- Docs show HTTP transport with `Authorization: Bearer ${mcpToken}` returned by `getMcpToken()`.
- Is this the same as running MCP locally?
- The gateway runs inside an isolated E2B sandbox VM, combining shell access with remote MCP tooling.
Related
Related
3 Indexed items
LiteLLM MCP Gateway
LiteLLM Proxy documentation describes an MCP Gateway that exposes list-tools, call-tools, prompts, and resources operations through a fixed endpoint while enforcing access by API key, team, or organization. Supported transports listed on docs.litellm.ai include Streamable HTTP, SSE, and stdio; operators can register HTTP, SSE, or stdio MCP servers through the LiteLLM UI or config.yaml after enabling database storage (`store_model_in_db` / `STORE_MODEL_IN_DB`). Release notes cited in the docs state LiteLLM v1.80.18 aligns with MCP protocol version 2025-11-25 and namespaces tools by MCP server name per SEP-986 naming rules for newly added servers. The gateway is positioned as a way to use MCP tools alongside all LiteLLM-supported chat models from Cursor or other OpenAI-compatible clients pointed at the proxy.
Apify MCP Server
Apify documents an official Model Context Protocol server hosted at https://mcp.apify.com that speaks Streamable HTTP in line with the current MCP specification; Apify warns that SSE transport was deprecated for removal April 1, 2026. Hosted clients authenticate through browser OAuth or by supplying Bearer tokens sourced from Console → Settings → Integrations (`APIFY_TOKEN`), can pin tool bundles via URL query (`?tools=actors,docs,apify/rag-web-browser` style examples reproduce Apify wording), optionally append `telemetry-enabled=false`, and benefit from inferred structured-output schemas surfaced for Actor tooling on hosted endpoints unlike the default stdio server. When MCP clients refuse remote transports, docs recommend `npx -y @apify/actors-mcp-server` with `APIFY_TOKEN` for stdio, Node.js ≥18, and adherence to documented per-user throughput (Apify cites up to thirty requests per second across Actor runs plus storage/documentation calls). Specialized payment modes (open x402 on Base plus Skyfire) appear as optional adjunct pages inside the broader integration handbook.
n8n MCP Server Trigger
The MCP Server Trigger is a first-party n8n core node that turns an n8n workflow into a Model Context Protocol server endpoint. Instead of chaining conventional trigger nodes, it connects only to tool nodes so remote MCP clients can list tools and invoke them over long-lived Server-Sent Events or streamable HTTP transports (stdio is explicitly unsupported). Each node exposes separate test and production MCP URLs, optional bearer or header authentication, and documentation explains how to proxy Claude Desktop through `npx mcp-remote` plus queue-mode caveats for multi-replica webhook deployments.