Docker MCP Gateway is the CLI plugin behind the MCP Toolkit in Docker Desktop. It runs each MCP server from the Docker MCP Catalog in its own container, gives every client (VS Code, Cursor, Claude Desktop and others) the same gateway configuration, keeps secrets out of environment variables through Docker Desktop's secrets management, and supports OAuth flows for servers that need them.
Who it suits
Individual developers and small teams who want MCP servers isolated in containers behind one local endpoint.
Strengths
- Each MCP server runs in an isolated container with minimal host privileges.
- One gateway configuration shared across MCP clients.
- Secrets handled by Docker Desktop rather than environment variables; built-in OAuth flows.
- Logging and call tracing.
Limits
- Built for a developer machine: no per-person identity, central policy or organisation-wide audit.
- The Toolkit expects Docker Desktop, which has its own subscription terms for commercial use.
Scores on each criterion
| Criterion | Score | What we found |
|---|---|---|
| Authentication | Not documented | Local gateway; no per-user identity documented. |
| Credential handling | Partial | Docker Desktop secrets and OAuth flows, on one machine. |
| Policy depth | Partial | Container isolation and minimal privileges; no per-user rules. |
| Audit | Partial | Logging, kept locally. |
| Observability | Partial | Call tracing; no OpenTelemetry documented in the README. |
| Deployment model | Strong | Docker Desktop, or containers with Docker CE. |
| Shadow usage discovery | Not documented | Not documented. |
| Total | 6/14 | Ranked #6 of 8 |
Strong Built in and documented (2 points)Partial Present with gaps, or limited scope (1 point)Not documented Not found in the public docs we reviewed (0 points)
What it costs
The plugin is MIT-licensed. Docker Desktop's terms apply; check docker.com/pricing.
Sources
Every score above comes from these public pages. Check them for changes since 11 November 2026.