Docker MCP Toolkit

官方

官方 Docker MCP 工具包，用於透過 Docker Desktop 和 Docker MCP 閘道發現、設定及執行容器化的 MCP 伺服器。

造訪 docker.com

你可以用 Docker Toolkit MCP 做什麼？

  • 集中管理 MCP 伺服器 — 請你的 AI 助手設定一個以 Docker 為基礎的集中式中樞，讓所有 AI 應用程式共享同一份設定，而非各自獨立配置。
  • 使用精選伺服器目錄 — 讓你的助手從 300 多個經過驗證、容器化的 MCP 伺服器中選取，這些伺服器具備版本控制與安全更新，也可為你的團隊建立自訂目錄。
  • 將伺服器組織成設定檔 — 請你的助手將伺服器分組（例如 GitHub 和 Playwright 用於網頁開發），並命名為可重複使用的設定檔，方便在不同用戶端間使用或與團隊成員共享。
  • 透過閘道連接 AI 用戶端 — 指示你的助手將來自 Claude Code、Cursor 或 Zed 的請求路由至 MCP Gateway，以進行集中式驗證與生命週期管理。

文件

Docker MCP Catalog and Toolkit

Model Context Protocol (MCP) is an open protocol that standardizes how AI applications access external tools and data sources. By connecting LLMs to local development tools, databases, APIs, and other resources, MCP extends their capabilities beyond their base training.

The challenge is that running MCP servers locally creates operational friction. Each server requires separate installation and configuration for every application you use. You run untrusted code directly on your machine, manage updates manually, and troubleshoot dependency conflicts yourself. Configure a GitHub server for Claude, then configure it again for Cursor, and so on. Each time you manage credentials, permissions, and environment setup.

Docker MCP features

The MCP Toolkit and MCP Gateway solve these challenges through centralized management. Instead of configuring each server for every AI application separately, you set things up once and connect all your clients to it. The workflow centers on three concepts: catalogs, profiles, and clients.

Catalogs are curated collections of MCP servers. The Docker MCP Catalog provides 300+ verified servers packaged as container images with versioning, provenance, and security updates. Organizations can create custom catalogs with approved servers for their teams.

Profiles organize servers into named collections for different projects. Your "web-dev" profile might use GitHub and Playwright; your "backend" profile, database tools. Profiles support both containerized servers from catalogs and remote MCP servers. Configure a profile once, then share it across clients or with your team.

Clients are the AI applications that connect to your profiles. Claude Code, Cursor, Zed, and others connect through the MCP Gateway, which routes requests to the right server and handles authentication and lifecycle management.

[!NOTE] MCP Gateway as part of Docker AI Governance is an invite-only feature. Contact Docker Sales to learn more.

Learn more