Container operations in conversation — inspect, run, debug and clean up Docker workloads.
The Docker MCP server puts container management on a conversational footing. Built by the community around the Docker SDK, it covers the daily verbs: list and inspect containers, run new ones, read logs, manage images, volumes and networks — the 80% of docker CLI usage that's really about asking "what's running and why is it unhappy?"
Debugging is where it earns its place. "Why does this container keep restarting?" becomes a real diagnostic session: the assistant checks the container state, reads the last hundred log lines, notices the OOM kill or the bad env var, and explains it. That beats copy-pasting docker logs output into a chat window — the assistant drives the investigation itself, following leads across containers.
It also does deployment-by-description: ask for "a WordPress with a MySQL backend on a shared network" and the server can compose the containers, volumes and network without you writing YAML. That's a party trick for production (use real compose files, please) but genuinely handy for spinning up throwaway environments while prototyping.
Since it talks to the Docker socket, it holds root-equivalent power over the host — treat it accordingly and keep tool-call confirmations on for anything destructive. Also worth knowing: Docker Desktop now ships an MCP Toolkit, which runs other MCP servers as containers — different job from this server, which manages Docker itself. If you want an assistant that tends your containers, this is the one.
DOCKER_HOST accepts ssh://user@host, so one config can tend a remote box. Remember that the assistant then holds that machine's socket too.Restart loops, port conflicts and OOM kills diagnosed from real logs and state, not guesswork.
Describe a stack and get containers, volumes and networking wired up for quick experiments.
Find what's eating disk — dangling images, dead containers, orphaned volumes — and clean it up.
| Tool | What it does |
|---|---|
| list_containers | List running (and stopped) containers with status |
| create_container / run_container | Start containers from images with ports, env and volumes |
| fetch_container_logs | Read a container's recent log output |
| stop_container / remove_container | Stop and clean up containers |
| list_images / pull_image | Manage local images |
| list_volumes / list_networks | Inspect volumes and networks |
{
"mcpServers": {
"docker": {
"command": "uvx",
"args": ["mcp-server-docker"]
}
}
}Needs access to the Docker socket — Docker Desktop or a running dockerd.
Python 3.12+ with uv, and a reachable Docker daemon. The server wields socket-level power — confirm destructive calls.
| Variable | Description | Required |
|---|---|---|
| DOCKER_HOST | Docker daemon address if not the default local sockete.g. unix:///var/run/docker.sock | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.