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를 통해 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