Docker MCP Gateway

Docker MCP Gateway is Docker's open-source control layer for running MCP servers in isolated containers and exposing them through a single gateway process. It sits underneath Docker Desktop's MCP Toolkit, but the same CLI plugin can also run outside Docker Desktop for teams that want Docker-managed MCP profiles, catalogs, and client connections.

What it does

Docker MCP Gateway groups MCP servers into profiles, starts them with Docker-managed isolation, and exposes them to clients such as Claude Desktop and VS Code through one consistent entry point. It also supports OCI-backed catalogs, dynamic tool discovery, OAuth-enabled servers, and runtime controls such as per-server CPU and memory limits.

How it works

The core pattern is AI client → Docker MCP Gateway → MCP servers in containers. Teams can pull servers from the Docker MCP Catalog, import compatible community registry entries, organize them into profiles, and then connect one or more MCP clients to the same profile instead of configuring each server separately in every client.

Where it fits

Docker MCP Gateway is best suited to teams that already operate around Docker and want MCP server lifecycle management, container isolation, signed images, and Docker-native workflows. It is stronger on packaging, local execution, and secure runtime defaults than on centralized enterprise governance features such as deep RBAC, immutable audit trails, or identity federation.

Limitations

• Screenshot evidence was unavailable during this draft because the screenshot service hit its request limit, so visual verification of the current UI is still pending.
• The gateway relies on Docker-centric workflows, which makes it less attractive for teams that do not already standardize on Docker or Kubernetes-style operations.
• Governance depth is lighter than security-first MCP gateways, so teams needing built-in policy enforcement, rich audit trails, or identity-aware access control will need extra tooling on top.
• The official docs position the Toolkit as beta in Docker Desktop 4.62+, so UI flows and product surface may still change quickly.