Skip to content
aicoolies logo
Docker logo

Docker MCP Gateway

Open-source Docker gateway for containerized MCP server orchestration

Docker MCP Gateway is Docker's open-source orchestration layer for Model Context Protocol servers. It gives MCP clients one gateway, launches catalog servers in isolated containers on demand, injects credentials, applies runtime restrictions, and routes tool requests. Catalogs and profiles let teams reuse approved server collections across clients, while Docker Desktop can run the gateway automatically with MCP Toolkit enabled.

About Docker MCP Gateway

Docker MCP Gateway is Docker's open-source orchestration layer for Model Context Protocol servers. Instead of configuring every server separately in each AI application, teams connect clients to one gateway that centralizes server configuration, routing, credentials, and access controls. Docker Desktop starts the gateway automatically when MCP Toolkit is enabled, while the same docker mcp CLI can be used directly for advanced Docker Engine and non-Desktop setups.

For local catalog servers, the gateway launches each MCP server on demand in an isolated Docker container. Docker's documentation describes restricted privileges, network access, and resource usage, plus credential injection, built-in logging, and call tracing. When a client requests a tool, the gateway identifies the responsible server, starts it if necessary, applies the configured restrictions, forwards the request, and returns the result through the same connection.

Catalogs and profiles provide the distribution model around the runtime. Docker's public catalog currently advertises 300+ verified servers packaged as container images with versioning, provenance, and security updates; custom catalogs can limit teams to approved servers. Profiles group containerized or remote servers for a project, support tool allowlists, and can be reused across clients such as Claude Code, Cursor, VS Code, and other MCP-compatible applications instead of duplicating configuration.

The strongest fit is a Docker-based team that wants repeatable MCP server packaging, a shared gateway endpoint, and tighter runtime isolation than launching community packages directly on a workstation. It still requires a Docker runtime and profile/catalog maintenance, and the MCP Catalog and Toolkit are documented as beta. Docker also distinguishes this MIT-licensed open-source gateway from the MCP Gateway capabilities sold as part of Docker AI Governance, which the official documentation labels invite-only; buyers should not treat those enterprise governance features as part of the free OSS runtime.

Pricing & Platform Specs

Pricing Summary

Docker MCP Gateway is free and open source as a standalone CLI plugin. For desktop GUI workflows via the MCP Toolkit in Docker Desktop, it is free for personal use, education, and small businesses under Docker Personal, while commercial use in larger organizations starts at $5 per user per month on Docker Pro.

full pricing breakdown →

Supported Platforms

Docker Desktop and Docker Engine; docker mcp CLI; stdio, SSE, and streaming transports; catalog, profile, client, secrets, logging, and call-tracing workflows.

Explore categories, tags & use cases

Categories

Side-by-Side Comparisons

Docker logo
Docker MCP Gateway
vs
Executor logo
Executor

Docker MCP Gateway vs Executor: Containerized Isolation vs Unified Tool Catalog for AI Agents

Docker MCP Gateway and Executor provide two distinct architectural solutions for orchestrating AI agent tools. While Docker MCP Gateway provides containerized OCI isolation and Docker Desktop integration for Model Context Protocol servers, Executor acts as a universal API gateway normalizing MCP, OpenAPI, and GraphQL into a single catalog. Here is an in-depth architectural and security comparison.

Docker MCP GatewayExecutor
Docker logo
Docker MCP Gateway
vs
Smithery logo
Smithery

Docker MCP Gateway vs Smithery: Secure Runtime or Managed Connect?

Docker MCP Gateway is the stronger default when teams need isolated MCP execution, centralized lifecycle control, credential injection, and call visibility. Smithery wins the managed discovery and OAuth carve-out, but Docker wins the core secure-runtime decision.

Docker MCP GatewaySmithery

Community experience

Sources & verification

Sources checked
Content verified

Verification dates are editorial checks. Routine CMS saves and automatic updatedAt timestamps do not advance them.

FAQ

What is Docker MCP Gateway?

Docker MCP Gateway is Docker's open-source orchestration layer for Model Context Protocol servers. It gives MCP clients one gateway, launches catalog servers in isolated containers on demand, injects credentials, applies runtime restrictions, and routes tool requests. Catalogs and profiles let teams reuse approved server collections across clients, while Docker Desktop can run the gateway automatically with MCP Toolkit enabled.

Is Docker MCP Gateway free?

Docker MCP Gateway offers a free tier alongside paid plans. Docker MCP Gateway is free and open source as a standalone CLI plugin. For desktop GUI workflows via the MCP Toolkit in Docker Desktop, it is free for personal use, education, and small businesses under Docker Personal, while commercial use in larger organizations starts at $5 per user per month on Docker Pro.

Is Docker MCP Gateway open source?

Yes — Docker MCP Gateway is open source.

Is Docker MCP Gateway still maintained?

Yes — Docker MCP Gateway is active. Its listing was last verified on August 26, 2026.

How does Docker MCP Gateway score in our review?

The published editorial review lists Docker MCP Gateway at 87/100 overall across speed, privacy, and developer experience. Check the review's evidence status and test metadata for its verification level.