Docker MCP Toolkit

官方

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

造訪 docker.com

你可以用 Docker Toolkit MCP 做什麼？

  • 瀏覽 MCP 目錄 — 請助手使用 list_servers 列出 Docker MCP 目錄中的可用伺服器。
  • 檢視伺服器 — 使用 get_server 查詢特定伺服器的版本、描述及執行環境設定等詳細資訊。
  • 管理設定檔 — 透過 create_profile、list_profiles 和 delete_profile 為不同專案建立、列出或刪除具名伺服器設定檔。
  • 將伺服器加入設定檔 — 使用 add_server_to_profile 將目錄中的伺服器附加至設定檔，以便 AI 用戶端可直接使用。
  • 連接用戶端 — 透過 register_client 將 Claude Code 或 Cursor 等 AI 應用程式註冊至設定檔。

文件

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