Docker MCP Toolkit

官方

用于通过 Docker Desktop 和 Docker MCP 网关发现、配置和运行容器化 MCP 服务器的官方 Docker MCP 工具包。

你可以用 Docker Toolkit MCP 做什么?

  • 集中管理 MCP 服务器 — 让您的 AI 助手搭建一个基于 Docker 的集中式枢纽,使所有 AI 应用共享同一配置,而无需逐个应用单独设置。
  • 使用精选服务器目录 — 让您的助手从 300 多个经过验证、容器化的 MCP 服务器中选取,这些服务器带有版本管理和安全更新,或为您的团队创建自定义目录。
  • 将服务器组织到配置文件中 — 让您的助手将服务器分组(例如,将 GitHub 和 Playwright 用于 Web 开发)到命名配置文件中,您可以在多个客户端中复用或与团队成员共享。
  • 通过网关连接 AI 客户端 — 指示您的助手将来自 Claude Code、Cursor 或 Zed 的请求路由到 MCP 网关,以实现集中式身份验证和生命周期管理。

文档

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