MCP server for Docker — manage containers, images, volumes, and compose services from your IDE
Runs on your machine from its package; the steps are below.

At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y mcp-docker-server
MCP client config
{
"mcpServers": {
"docker": {
"command": "npx",
"args": [
"-y",
"mcp-docker-server"
]
}
}
}Control Docker containers, images, and services from your AI coding assistant. List, start, stop, read logs, run commands inside containers, and check resource usage.
npx mcp-docker-server
Compatible with Claude Desktop, Cursor, VS Code Copilot, and any MCP-compatible client. No API keys needed. Connects to your local Docker socket automatically.

Demo built with remotion-readme-kit
If you work with Docker daily, you know the routine: switch to a terminal, type docker ps, scroll through logs, copy container IDs, restart services. It adds up. This MCP server lets your AI assistant handle those tasks for you while you stay focused on code. Ask it to check which containers are running, pull up logs from a failing service, or restart something that got stuck. It talks to Docker's API through the local socket, so there's nothing to configure and no credentials to manage.
| Tool | What it does |
|---|---|
list_containers | List running (or all) containers with status, ports, and image info |
container_logs | Get recent logs from a container |
start_container | Start a stopped container |
stop_container | Stop a running container |
restart_container | Restart a container |
remove_container | Remove a container (with optional force) |
exec_command | Execute a command inside a running container |
container_stats | Get live CPU, memory, and network stats |
list_images | List all Docker images on the host |
remove_image | Remove a Docker image |
Add to .cursor/mcp.json:
{
"mcpServers": {
"docker": {
"command": "npx",
"args": ["-y", "mcp-docker-server"]
}
}
}
Add to claude_desktop_config.json:
{
"mcpServers": {
"docker": {
"command": "npx",
"args": ["-y", "mcp-docker-server"]
}
}
}
Add to user settings or .vscode/mcp.json:
{
"mcp": {
"servers": {
"docker": {
"command": "npx",
"args": ["-y", "mcp-docker-server"]
}
}
}
}
ls -la /app inside the web container"/var/run/docker.sock (Linux/macOS) or the named pipe on WindowsThis repo is an Agent Plugins 1.0.0 package: plugin.json, portable mcp.json, and skills/ ship together with the MCP server.
For Cursor, clone the repo and copy or symlink it to ~/.cursor/plugins/local/mcp-server-docker, then reload the window. Skills and MCP show up under Customize > Plugins.
The Cursor and VS Code install buttons above still work: they add the same npx -y mcp-docker-server stdio server as manual JSON.
The npm package for this MCP server (repo name mcp-server-docker). It talks to your local Docker socket to list containers, tail logs, exec commands, and manage images.
Yes. The daemon must be up and the MCP process must reach docker.sock (or the Windows named pipe).
Treat stop/remove/restart as destructive. Confirm with the user before changing production workloads.
Yes. Use ~/.cursor/plugins/local/mcp-server-docker so the bundled docker-management skill loads with the MCP config.
No. Only local Docker access.
git clone https://github.com/ofershap/mcp-server-docker.git
cd mcp-server-docker
npm install
npm test
npm run build
More MCP servers and developer tools on my portfolio.
README built with README Builder
MIT © 2026 Ofer Shapira