E2B and Docker MCP: setup for sandboxed Claude Code

Docker's Oleg Šelajev and E2B's Jonas Scholz explain how E2B sandboxes connect to Docker's MCP Catalog and Gateway. Scholz describes E2B as open source infrastructure that gives an AI agent access to an isolated Linux virtual machine. The walkthrough uses cloud sandboxes. He says developers can host the backend themselves, but warns that setup involves considerably more than a single Docker command.

The example creates a sandbox through an SDK, configures MCP servers and runs Claude Code inside it. The Gateway and selected server containers run in the same sandbox. Scholz also explains how a local client can connect to the remote Gateway with authentication. JavaScript and Python SDKs provide typed configuration generated from the catalog.

Claude Code searches for research papers and author information, then creates an HTML summary served through a Python HTTP server. The demo runs into a five-minute sandbox lifetime and an explicit sandbox kill before the presenters eventually show the page. They describe public HTTP serving as a demonstration approach and suggest storing output in a database or S3 instead.

The discussion covers reusable templates, including an MCP template with the Gateway, npm and Python installed. In this November 2025 recording, remote catalog servers are supported, but Scholz says OAuth does not work with the E2B Gateway integration shown; it uses API keys or tokens.