Universal Docker MCP server for AI assistants (Cursor, Claude Desktop)
If you already use Docker, the docker mcp server is the piece that lets your assistant work with it directly. Universal Docker MCP server for AI assistants (Cursor, Claude Desktop).
Universal Docker MCP server for AI assistants (Cursor, Claude Desktop). Manage Docker containers, execute commands, query databases, and handle environment configurations — all through natural language.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
docker_container_list — List all containers (grouped by project)docker_container_start — Start a containerdocker_container_stop — Stop a containerdocker_container_restart — Restart a containerdocker_container_logs — View container logsdocker_container_stats — Get container resource usagedocker_compose_up — Start entire stackdocker_compose_down — Stop entire stackdocker_resource_list — List Docker images, volumes, or networksdocker_db_query — Execute SQL query or database commanddocker_db_backup — Create database backupdocker_db_restore — Restore from backupConfiguration is passed through the environment: DOCKER_MCP_AUTO_DISCOVER, DOCKER_MCP_MASK_SECRETS, DOCKER_MCP_PROFILES_FILE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
@hypnosis/docker-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of database access 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 — docker_container_list, docker_container_start, docker_container_stop and 11 more — is a fair guide to whether it matches your workflow. It is maintained by hypnosis; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| docker_container_list | List all containers (grouped by project) |
| docker_container_start | Start a container |
| docker_container_stop | Stop a container |
| docker_container_restart | Restart a container |
| docker_container_logs | View container logs |
| docker_container_stats | Get container resource usage |
| docker_compose_up | Start entire stack |
| docker_compose_down | Stop entire stack |
| docker_resource_list | List Docker images, volumes, or networks |
| docker_db_query | Execute SQL query or database command |
| docker_db_backup | Create database backup |
| docker_db_restore | Restore from backup |
| docker_db_status | Show database status |
| docker_env_list | List environment variables (with secret masking) |
{
"mcpServers": {
"docker-1": {
"command": "npx",
"args": ["-y", "@hypnosis/docker-mcp-server"],
"env": {
"DOCKER_MCP_AUTO_DISCOVER": "your-value",
"DOCKER_MCP_MASK_SECRETS": "your-value",
"DOCKER_MCP_PROFILES_FILE": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DOCKER_MCP_AUTO_DISCOVER | Configuration value read at startup. | Optional |
| DOCKER_MCP_MASK_SECRETS | Credential the server authenticates with. | Yes |
| DOCKER_MCP_PROFILES_FILE | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.