Docker MCP Toolkit

官方

用于通过 Docker Desktop 和 Docker MCP 网关发现、配置和运行容器化 MCP 服务器的官方 Docker 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将AI应用程序（如Claude Code或Cursor）注册到配置文件。

文档

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