docker-mcp-server
Provides tools for managing Docker containers, images, Compose stacks, health checks, logs, and more, enabling agents to keep containers running and perform operations through the Docker API.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@docker-mcp-serverlist running containers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@supernova123/docker-mcp-server
The Docker MCP server designed for agents that need their containers to stay running.
Without this: Your agent deploys a container, it crashes at 3am, and nobody notices until the user complains. Compose stacks drift. Health checks are manual. Logs are scattered across terminals.
With this: Your agent checks health, watches for readiness, restarts crashed containers, and follows logs, all through a single MCP interface. Containers stay running because your agent knows how to keep them running.
Why This Server?
There are 11+ Docker MCP servers on npm. Most are stale, GPL-licensed, or only cover basic CRUD. This one is different:
This server | ckreiling/mcp-server-docker | docker/hub-mcp | |
License | MIT | GPL-3.0 | Apache-2.0 |
Last updated | Active | Jun 2025 (stale) | Active |
Health checks | ✅ HTTP/TCP/exec probes | ❌ | ❌ |
Auto-restart | ✅ set_restart_policy | ❌ | ❌ |
Compose lifecycle | ✅ up/down/ps/logs/restart | ❌ | ❌ |
Log streaming | ✅ tail + timestamp filter | Basic | Basic |
Agent positioning | ✅ Built for agents | Generic Docker | Registry API |
Related MCP server: Docker MCP Server
Quick Start
One command to run:
npx @supernova123/docker-mcp-serverClaude Desktop / Cursor / VS Code Config
Add to your MCP settings:
{
"mcpServers": {
"docker": {
"command": "npx",
"args": ["-y", "@supernova123/docker-mcp-server"]
}
}
}Claude Code
claude mcp add docker -- npx -y @supernova123/docker-mcp-serverTools
Container Lifecycle
Tool | Description |
| List containers with filters (state, label, name) |
| Get detailed container config and state |
| Start a stopped container |
| Stop a running container |
| Restart a container |
| Remove a container (with force option) |
| Stop, remove, and re-create a container with same config |
| Create + start a container in one call |
Image Management
Tool | Description |
| List images with optional filters |
| Pull an image from a registry |
| Build an image from a Dockerfile |
| Remove an image |
Docker Compose
Tool | Description |
| Bring up a Compose stack |
| Tear down a Compose stack |
| List service states |
| Tail Compose service logs |
| Restart Compose services |
Health & Self-Healing
Tool | Description |
| Run a health probe (HTTP, TCP, exec) |
| Poll health until healthy or timeout |
| Change restart policy on a running container |
Logs & Observability
Tool | Description |
| Get container logs with tail/timestamp filtering |
| CPU, memory, network, block I/O snapshot |
Exec
Tool | Description |
| Run a command inside a running container |
Networks & Volumes
Tool | Description |
| List Docker networks |
| List Docker volumes |
Requirements
Node.js 18+
Docker daemon running locally (or remote via DOCKER_HOST)
Docker socket accessible at
/var/run/docker.sock
Security
Read-only by default: all container and image tools read state; write operations (start/stop/remove) require explicit tool calls
No API keys needed: connects to local Docker daemon via socket
No network access: all operations are local Docker API calls
MIT License: fully auditable
License
MIT
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/friendlygeorge/docker-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server