More than just a fully featured MCP server that lets AI agents manage the full surface of Docker — containers, images, networks, volumes, swarm
More than just a fully featured MCP server that lets AI agents manage the full surface of Docker — containers, images, networks, volumes, swarm services, secrets, configs, nodes, plugins, etc., it helps you create workfl. Exposed over MCP by the docker mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
install. on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
Linux — ** -v /var/run/docker.sock:/var/run/docker.sock (rootless: -v $XDG_RUNTIME_DIR/docker.sock:/var/run/docker.sock)Variant — Tagsno-scout — :no-scout, :-no-scoutYou will need 4 environment variables: DOCKER_HOST, DOCKER_TLS_VERIFY, DOCKER_CERT_PATH, DOCKER_MCP_SERVER_HOSTS. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Note: If you're using the containerized MCP server or MCPB bundle, the Python and uv requirements are taken care of for you. - A running Docker daemon reachable from the host that runs the server (the standard DOCKER_HOST / unix socket conventions apply) - Python ≥ 3.14 - uv for dependency management
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Docker's toolset — Linux, Variant, no-scout — is a fair guide to whether it matches your workflow. It is maintained by L337.org; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Linux | ** -v /var/run/docker.sock:/var/run/docker.sock (rootless: -v $XDG_RUNTIME_DIR/docker.sock:/var/run/docker.sock). |
| Variant | Tags |
| no-scout | :no-scout, :<version>-no-scout |
{
"mcpServers": {
"docker-mcp-server": {
"command": "uvx",
"args": ["docker-mcp-server"],
"env": {}
}
}
}Configuration as documented by the project. Restart the client after saving.
Note: If you're using the containerized MCP server or MCPB bundle, the Python and uv requirements are taken care of for you. - A running Docker daemon reachable from the host that runs the server (the standard DOCKER_HOST / unix socket conventions apply) - Python ≥ 3.14 - uv for dependency management
| Variable | Description | Required |
|---|---|---|
| DOCKER_HOST | Endpoint or connection string the server talks to. | Optional |
| DOCKER_TLS_VERIFY | Configuration value read at startup. | Optional |
| DOCKER_CERT_PATH | Filesystem location the server is allowed to use. | Optional |
| DOCKER_MCP_SERVER_HOSTS | Endpoint or connection string the server talks to. | 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.