Why run MCP servers in containers instead of directly with npx/uvx?

Docker MCP Gateway

Run and manage MCP servers as isolated Docker containers with one gateway.

Last updated July 18, 2026

Cloud & InfrastructureLocal · stdioGo1.5k

Overview

Docker's official MCP Gateway runs MCP servers as isolated Docker containers instead of granting npx/uvx servers direct host access, providing a single gateway configuration, secrets management via Docker Desktop, and OAuth handling across every client.

Use cases

Run untrusted or third-party MCP servers in isolated containers instead of directly on your host.

Manage secrets for multiple MCP servers centrally through Docker Desktop.

Give every AI client on your machine the same consistent set of MCP servers via one gateway.

Install

{
  "mcpServers": {
    "docker-mcp-gateway": {
      "command": "docker",
      "args": [
        "mcp",
        "gateway",
        "run"
      ]
    }
  }
}

FAQ

Container isolation limits what a (potentially untrusted) MCP server can access on your host, and centralizes secrets management instead of scattering API keys across per-server environment variables.