Docker Mcp
Operate local or dev Docker engines from Claude Code—list containers, manage images, networks, volumes, and registries without shell hopping.
Overview
docker-mcp is a MCP server for the Operate phase that lets agents manage Docker containers, images, networks, volumes, and registries via stdio.
What is this MCP server?
- stdio MCP package @alisaitteke/docker-mcp on npm at version 0.2.4
- Tools span containers, images, networks, volumes, and registries
- Local Docker daemon control suitable for dev sandboxes and solo deploy pipelines
- GitHub-hosted open source server schema without required remote API key
- Package version 0.2.4 on npm registry
- Transport type stdio via @alisaitteke/docker-mcp
- Tool scope includes containers, images, networks, volumes, and registries per description
Community signal: 2 GitHub stars.
What problem does it solve?
You waste context switching between your agent and a terminal every time you need to inspect or change Docker resources.
Who is it for?
Indie builders who dockerize apps locally and want Claude Code or Cursor to handle routine container and image housekeeping.
Skip if: Production-only Kubernetes operators who never touch local Docker, or environments without Docker Engine installed.
What do I get? / Deliverables
Your agent can run Docker management operations through MCP tools while you stay in one coding or incident-response session.
- Agent-invokable Docker container and image operations
- Network, volume, and registry inspection or changes from MCP
- Reduced terminal context switching during infra tweaks
Recommended MCP Servers
Journey fit
Canonical shelf is Operate because day-to-day container lifecycle management maps to running infrastructure, not initial app coding. Infra subphase covers containers, images, networks, volumes, and registry operations exposed as MCP tools.
How it compares
Local Docker Engine MCP bridge, not a cloud PaaS deploy skill or Kubernetes control plane server.
Common Questions / FAQ
Who is io.github.alisaitteke/docker-mcp for?
Developers with Docker on their machine who want MCP agents to manage containers, images, networks, volumes, and registries safely from chat.
When should I use io.github.alisaitteke/docker-mcp?
Use it during operate and iterate loops when debugging stacks, cleaning images, or verifying registry tags without leaving your agent.
How do I add io.github.alisaitteke/docker-mcp to my agent?
Add the npm package @alisaitteke/docker-mcp (0.2.4) as a stdio MCP server in your client config and ensure Docker daemon is running locally.