
Docker Mcp
io.github.alisaitteke由 GitHub 账号 alisaitteke 发布v0.2.4更新于 Oct 24, 2026
MCP server for managing Docker containers, images, networks, volumes, and registries
发布方自己的服务:Docker Recipes
概览
本地 MCP 服务器,让 AI 助手用自然语言管理 Docker 容器、镜像、网络、卷、Compose 项目与镜像仓库。
- 可以做什么
- 列出、创建、启动、停止、重启、终止、暂停、检查与删除容器,并查看日志和统计
- 拉取、推送、打标签、构建、检查与删除镜像,包括历史与分层信息
- 创建、检查与删除网络和卷,并连接或断开容器
- 在运行中的容器内执行命令并查看 exec 实例
- 启动、停止、重启、构建与校验 Docker Compose 服务,查看其日志与状态
- 查询系统信息与版本、监听事件、清理未使用资源,并搜索或登录 Docker Hub 与 GHCR
- 适用场景
- 适合希望让助手直接查看和操作本地或远程 Docker 环境的场景,例如确认哪些容器在运行、读取日志、在容器内执行命令,或启停 Compose 服务而无需切换到终端。
- 运行要求
- 通过 npx 或全局 npm 安装以 stdio 在本地运行;需要 Node.js 18 或更高版本,以及可访问的运行中 Docker 守护进程。套接字路径按平台自动检测;连接远程主机需设置 DOCKER_HOST、DOCKER_PORT、DOCKER_PROTOCOL、DOCKER_SOCKET_PATH、DOCKER_CERT_PATH 和 DOCKER_TLS_VERIFY,并可能需要网络访问与 TLS 证书。
安装
在 SourceWeft 中
- 打开 控制台中的 Docker Mcp,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Docker MCP Server
Powerful Docker management for AI assistants
A comprehensive Model Context Protocol (MCP) server that empowers AI assistants like Cursor, Claude Desktop, and other MCP-compatible clients to seamlessly manage Docker containers, images, networks, volumes, and registries through natural language interactions.
Why Docker MCP Server?
- Zero Configuration - Works out of the box with
npx, no installation needed - Safety First - Two-step confirmation for destructive operations
- Cross-Platform - Works on Windows, Linux, and macOS with automatic Docker socket detection
- Comprehensive - Full Docker API coverage including Compose, registries, and system operations
- AI-Native - Designed specifically for AI assistants with clear, structured responses
[Features] Features
Container Management
- Full lifecycle control: Create, start, stop, restart, kill, and remove containers
- Monitoring: Real-time logs, statistics, and container inspection
- Advanced operations: Pause/unpause, exec commands, and resource management
Image Management
- Registry operations: Pull, push, tag, and remove images
- Build support: Build images from Dockerfiles with full configuration
- Inspection: Detailed image history, layers, and metadata
Network Management
- Network operations: Create, remove, and inspect Docker networks
- Container connectivity: Connect/disconnect containers from networks
- Network discovery: List and filter networks with advanced options
Volume Management
- Volume operations: Create, remove, and inspect volumes
- Data persistence: Manage persistent storage for containers
- Volume inspection: Detailed volume information and mount points
System Operations
- System information: Docker daemon info, version, and capabilities
- Resource cleanup: Prune unused images, containers, volumes, and networks
- Event monitoring: Real-time Docker event stream
Container Execution
- Command execution: Run commands in running containers
- Interactive sessions: Create and manage exec instances
- Output streaming: Real-time command output and logs
Registry Integration
- Docker Hub: Search repositories, list tags, authenticate, pull/push images
- GitHub Container Registry (GHCR): Full authentication and image management
- Multi-registry support: Seamlessly work with multiple registries
Docker Compose Support
- Multi-container management: Start, stop, restart compose services
- Service monitoring: View logs and status of compose services
- Build operations: Build compose services with dependency management
- Configuration validation: Parse and validate docker-compose.yml files
Safety Features
- Two-step confirmation for all destructive operations
- Resource preview: See what will be deleted before confirmation
- Dual confirmation methods:
- Confirm parameter (default): Works everywhere, simple and reliable
- MCP Elicitation API (advanced): Interactive form-based confirmation for better UX
[Installation] Installation
Via npx (Recommended)
Local Installation
Or install locally in your project:
[Quick Start] Quick Start
With Cursor
- Add to your Cursor MCP configuration (usually in
.cursor/mcp.jsonor similar):
- Restart Cursor and start managing Docker with AI!
With Claude Desktop
- Add to your Claude Desktop configuration:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
- macOS:
- Restart Claude Desktop and start managing Docker with AI!
Local Development and Testing
Prerequisites
- Node.js 18.0.0 or higher
- Docker daemon running
- npm or yarn
Setup
- Clone the repository:
- Install dependencies:
- Build the project:
Running Locally
Method 1: Using npm start (after build)
Method 2: Using npm run dev (development mode with tsx)
This uses tsx to run TypeScript directly without building.
Method 3: Direct execution
Method 4: Using the binary
Development Workflow
- Make changes to source files in
src/ - Build the project:
- Test the changes:
- Check for TypeScript errors:
- Lint the code:
Troubleshooting
Docker connection issues:
- Ensure Docker daemon is running:
docker ps - Linux/macOS: Check Docker socket permissions:
ls -la /var/run/docker.sock - Windows: Ensure Docker Desktop is running and named pipe is accessible
- For remote Docker, set environment variables:
DOCKER_HOST,DOCKER_CERT_PATH, etc. - macOS: If
/var/run/docker.sockdoesn't exist, try~/.docker/run/docker.sock(Docker Desktop 4.0+)
Build errors:
- Clear node_modules and reinstall:
rm -rf node_modules && npm install - Check TypeScript version compatibility
- Ensure all dependencies are installed:
npm install
Runtime errors:
- Check that Docker is accessible:
docker version - Verify the build was successful:
ls -la dist/ - Check server logs (errors are written to stderr)
[Configuration] Configuration
The server automatically detects the operating system and uses the appropriate Docker socket path:
Platform-Specific Defaults
- Linux:
/var/run/docker.sock(Unix socket) - macOS:
/var/run/docker.sockor~/.docker/run/docker.sock(Docker Desktop 4.0+) - Windows:
//./pipe/docker_engine(Named pipe)
Connection Methods (in order of priority)
-
Environment variables (highest priority):
DOCKER_HOST- Docker daemon host (e.g.,tcp://localhost:2376,npipe:////./pipe/docker_engine)DOCKER_PORT- Docker daemon portDOCKER_PROTOCOL- Protocol (httporhttps)DOCKER_SOCKET_PATH- Path to Docker socket (overrides platform default)DOCKER_CERT_PATH- Path to Docker certificates directoryDOCKER_TLS_VERIFY- Enable TLS verification (1or0)
-
Platform-specific defaults (automatic detection):
- Linux:
/var/run/docker.sock - macOS:
/var/run/docker.sock(or~/.docker/run/docker.sockif available) - Windows:
//./pipe/docker_engine
- Linux:
Windows Configuration
On Windows, Docker Desktop uses named pipes. The server automatically detects Windows and uses the correct path. You can also explicitly set:
Remote Docker Host
To connect to a remote Docker host:
[Available Tools] Available Tools
Container Tools
docker_list_containers- List all containersdocker_create_container- Create a new containerdocker_start_container- Start a containerdocker_stop_container- Stop a containerdocker_restart_container- Restart a containerdocker_kill_container- Kill a containerdocker_remove_container- Remove a containerdocker_inspect_container- Get container detailsdocker_container_logs- Get container logsdocker_container_stats- Get container statisticsdocker_pause_container- Pause a containerdocker_unpause_container- Unpause a container
Image Tools
docker_list_images- List all imagesdocker_pull_image- Pull an image from registrydocker_push_image- Push an image to registrydocker_tag_image- Tag an imagedocker_remove_image- Remove an imagedocker_inspect_image- Get image detailsdocker_image_history- Get image history
Network Tools
docker_list_networks- List all networksdocker_create_network- Create a networkdocker_remove_network- Remove a networkdocker_inspect_network- Get network detailsdocker_connect_container- Connect container to networkdocker_disconnect_container- Disconnect container from network
Volume Tools
docker_list_volumes- List all volumesdocker_create_volume- Create a volumedocker_remove_volume- Remove a volumedocker_inspect_volume- Get volume details
System Tools
docker_system_info- Get Docker system informationdocker_version- Get Docker versiondocker_prune_system- Prune all unused resourcesdocker_prune_images- Prune unused imagesdocker_prune_containers- Prune stopped containersdocker_prune_volumes- Prune unused volumesdocker_prune_networks- Prune unused networks
Exec Tools
docker_exec- Execute a command in a containerdocker_inspect_exec- Get exec instance details
Compose Tools
docker_compose_up- Start Docker Compose servicesdocker_compose_down- Stop and remove Docker Compose servicesdocker_compose_ps- List Docker Compose servicesdocker_compose_logs- View output from Docker Compose servicesdocker_compose_config- Parse and validate docker-compose.yml filedocker_compose_build- Build Docker Compose servicesdocker_compose_restart- Restart Docker Compose servicesdocker_compose_stop- Stop Docker Compose servicesdocker_compose_start- Start Docker Compose services
Registry Tools
dockerhub_search- Search Docker Hubdockerhub_get_tags- Get repository tags from Docker Hubdockerhub_authenticate- Authenticate with Docker Hubdockerhub_pull- Pull from Docker Hubdockerhub_push- Push to Docker Hubghcr_authenticate- Authenticate with GitHub Container Registryghcr_pull- Pull from GHCRghcr_push- Push to GHCR
[Examples] Examples
List running containers
Create and start a container
Then start it:
Pull an image from Docker Hub
Search Docker Hub
Execute a command in a container
Start Docker Compose services
View Compose logs
Removing Resources with Confirmation
All destructive operations (remove, kill, prune) support two confirmation methods:
Method 1: Confirm Parameter (Default - Works Everywhere)
Step 1: Preview (without confirm)
This returns volume details and a warning message.
Step 2: Confirm (with confirm=true)
This actually removes the volume.
Method 2: MCP Elicitation API (Advanced - Better UX)
If your MCP client (Cursor, Claude Desktop) supports Elicitation API, you can use interactive confirmation:
This will show an interactive confirmation dialog in the client (if supported). The client will display a form asking for confirmation, and the operation proceeds only if the user accepts.
Note: Elicitation API support depends on the MCP client. If the client doesn't support it, the server automatically falls back to the confirm parameter method.
Operations requiring confirmation:
docker_remove_volume- Remove volumesdocker_remove_container- Remove containersdocker_kill_container- Kill containersdocker_remove_image- Remove imagesdocker_remove_network- Remove networksdocker_prune_system- Prune all unused resourcesdocker_prune_images- Prune unused imagesdocker_prune_containers- Prune stopped containersdocker_prune_volumes- Prune unused volumesdocker_prune_networks- Prune unused networks
Testing the Server
Quick Test
- Build the project:
- Use the test script:
Or test manually:
- Test Docker connection:
If Docker is running, you should see:
- Test with a simple MCP request (using jq for JSON formatting):
Note: The server communicates via stdio, so it will wait for JSON-RPC requests. Press Ctrl+C to exit.
Manual Testing Steps
- Start the server:
-
In another terminal, test with curl (if using HTTP transport) or use an MCP client
-
Verify Docker operations work:
- List containers: Use
docker_list_containerstool - Check system info: Use
docker_system_infotool
- List containers: Use
Integration Testing
For full integration testing, you'll need an MCP client. The server communicates via stdio (standard input/output), so it's designed to work with MCP-compatible clients like:
- Cursor IDE
- Claude Desktop
- Custom MCP clients
Debugging
Enable verbose logging by checking stderr output. The server writes errors and status messages to stderr:
[Requirements] Requirements
- Node.js 18.0.0 or higher
- Docker daemon running and accessible
- Supported Platforms:
- Linux (x64, ARM64)
- macOS (Intel, Apple Silicon)
- Windows (x64, ARM64)
- For remote Docker: Proper network access and TLS certificates (if using TLS)
Platform-Specific Notes
- Linux: Requires Docker daemon with Unix socket at
/var/run/docker.sock - macOS: Works with Docker Desktop. Automatically detects socket location.
- Windows: Works with Docker Desktop. Uses named pipe
//./pipe/docker_engine
Quick Start (Local Development)
License
MIT
Testing with MCP Clients
Testing with Cursor (Local Development)
If you're developing locally and want to test with Cursor:
- Build the project:
- Add to Cursor MCP configuration (usually in
.cursor/mcp.jsonor similar):
Or if using the binary:
Testing with Claude Desktop (Local Development)
If you're developing locally and want to test with Claude Desktop:
- Build the project:
- Add to Claude Desktop configuration:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
- macOS:
Testing with MCP Inspector (CLI)
You can test the server using MCP Inspector or any MCP client:
[Contributing] Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
来源:README.md,提交 b4f9de5
工具
0版本历史
1- v0.2.4最新Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。
其他 Docker 集成
Docker Recipes
recipes.docker官方发布者
一个远程 MCP 服务器,让助手搜索并获取可直接运行、用于自托管和家庭实验室的 Docker Compose 方案。

XenMCP Docker agent
com.xenmcp
面向单台 Docker 主机的只读 MCP 服务器:让助手列出并检查容器、读取日志、查看实时统计和近期事件,不执行命令也不做变更。

Reverse Engineer Anything (Docker)
由 GitHub 账号 psyb0t 发布
以 Docker 打包的 REA 逆向工程服务器,让助手反编译 APK、检查二进制文件并通过 adb 操作 Android 设备。

Docker Hub Mcp
由 GitHub 账号 mrfentmen 发布
查询 Docker Hub 上的镜像、标签和拉取次数,让助手无需 API 密钥即可核查容器镜像。

Docker Image Shape
由 GitHub 账号 sadri-dridi 发布
远程 MCP 服务器,提供一组小型、基本无状态的校验工具:Docker 镜像名格式、URL 与主机名解析、HTTP 状态探测、时间与算术。