Docker MCP and E2B: Claude Code sandbox setup

Learn to connect Claude Code to Docker MCP tools in an E2B cloud sandbox, then test GitHub access with MCP Inspector over streamable HTTP.

Player not loading? Watch on YouTube

This tutorial demonstrates Docker MCP tools in an E2B cloud sandbox. The example connects Claude Code to GitHub to inspect repositories and to Notion to save summaries. It uses a hosted environment rather than showing how to run models locally.

Setup starts with an E2B account and API keys in environment variables. The example repository also needs an Anthropic API key, a Notion integration token and a GitHub token. The code selects MCP servers through configuration and uses the E2B API to create and manage the sandbox. Claude Code then connects to the MCP toolkit inside it.

The demonstration asks the coding assistant to list the speaker's repositories and summarize the top three in a Notion page. The speaker runs it without permission prompts, citing sandbox isolation as the reason. That is the speaker's safety rationale, not evidence that isolation eliminates every risk.

Running uv run main prints an MCP Gateway URL and an authorization header. The speaker enters those details in MCP Inspector, selects streamable HTTP, lists the tools and tests a GitHub user lookup. The lookup returns the configured account, and the console later reports that the repository summaries are in Notion. The walkthrough covers configuration and connection checks; it does not demonstrate an offline deployment.