Docker MCP Gateway
1,588 starsDocker's official MCP toolkit and gateway (the docker-mcp CLI plugin): pick servers from the Docker MCP Catalog (hub.docker.com/mcp), each running in an isolated Docker container, and the gateway aggregates their tools, resources and prompts behind a single interface for all MCP clients — with built-in secrets management, OAuth flows, dynamic tool discovery and call tracing. Requires Docker Desktop 4.59+ with the MCP Toolkit enabled.
- First published：2025-04-22
- data as of：
- 2026-09-30
- Licence：
- MIT
- Transport：
- stdio / sse / http
- Primitives exposed：
- tools / resources / prompts
What it can touch
The gateway pulls and runs catalog container images, manages each server's secrets (API keys held by Docker Desktop), and exposes every enabled server's tools through one aggregate surface. What real systems get touched depends on which catalog servers you enable — each arrives with its own credentials and access scope.
Risk
Container isolation caps each server's direct host privileges (README: npx/uvx servers get minimal host privileges), but isolation is not harmlessness: every catalog server is a third-party supply-chain node, and the gateway merges their tools into one large attack surface — with centralized secrets making it a high-value target. Due-diligence each catalog server before enabling it.
Install prompt
安裝 Docker Desktop 4.59 以上版本並啟用 MCP Toolkit 功能（官方 README 有步驟與截圖），在 Toolkit 介面裡從 Docker MCP Catalog 選取並設定你要的 server，然後讓你的 MCP 客戶端連到 gateway。README 記載 gateway 可服務單一客戶端，或以 sse／streaming 傳輸同時服務多個客戶端。Paste this to your agent. It deliberately contains no tool subcommands — check the tool's official docs for commands.