🐳 Docker MCP Server
Chat with your Docker host. A Model Context Protocol server that turns any MCP‑capable AI — Claude Desktop, Cursor, Continue, Zed — into a natural‑language DevOps copilot for Docker & Docker Compose.
“Restart the api container.” · “Why did web crash — show me the last 100 log lines.” · “Deploy the stack in ./prod and confirm it’s healthy.”
Designed, built & maintained by SoyRage Agency · https://soyrage.es/
⚡ New here? Install in one command → Quick install.
✨ New in this release
See the roadmap for what comes next.
📑 Table of contents
- Quick install (one command)
- Run it over the network (HTTP)
- Diagnostics
- Guided workflows (prompts & resources)
- What is this?
- Why it exists
- Feature overview
- The interactive panel
- The terminal UI (TUI)
- Monitoring: Prometheus, Zabbix & more
- Modular plugin architecture
- How it works
- Requirements
- Installation
- Connecting to your AI client
- Configuration reference
- Connecting to remote / TLS daemons
- Security model
- Complete tool reference
- Example conversations
- Project structure
- Design principles
- Development
- Troubleshooting & FAQ
- Roadmap
- Contributing
- About SoyRage Agency
⚡ Quick install (one command)
Already use an MCP client? Point it at the published package — nothing to clone or build:
"docker": { "command": "npx", "args": ["-y", "@soyrageagency/docker-mcp"], "env": { "DOCKER_MCP_READONLY": "false" } }Or open the live web panel straight away:
npx -y -p @soyrageagency/docker-mcp docker-mcp-panel
Option A — standalone binary (no Node, no npm) · recommended for the CLI/TUI/panel
Since v1.1 you can install a single self-contained ragedocker executable — a Node runtime and the whole app fused into one file. Nothing else to install.
Windows (PowerShell):
irm https://raw.githubusercontent.com/soyrageagency/docker-mcp-server/main/scripts/install.ps1 | iex
macOS / Linux:
curl -fsSL https://raw.githubusercontent.com/soyrageagency/docker-mcp-server/main/scripts/install.sh | sh
Then just run ragedocker for an interactive menu, or ragedocker tui / ragedocker panel / ragedocker ia login. Re-run the installer any time to update. (How it's built and how to reuse this across repos: docs/DISTRIBUTION.md.)
Option B — via Node · configures Claude Desktop for you
Prefer the MCP-server-for-Claude-Desktop path? The installer clones the project, builds it, and configures Claude Desktop for you — no manual JSON editing. You need Git and Node.js ≥ 18.
Windows (PowerShell):
irm https://raw.githubusercontent.com/soyrageagency/docker-mcp-server/main/install.ps1 | iex
macOS / Linux:
curl -fsSL https://raw.githubusercontent.com/soyrageagency/docker-mcp-server/main/install.sh | bash
Already cloned the repo? Just run:
npm run setup # builds + configures Claude Desktop
Then restart Claude Desktop and ask: “What Docker containers are running?” 🎉
The installer backs up your existing config and merges the entry, so any other MCP servers you have are preserved. Prefer to see the snippet without writing anything? node scripts/install.mjs --print.
🧭 What is this?
The Model Context Protocol (MCP) is an open standard that lets AI assistants talk to external tools through a well‑defined JSON‑RPC interface. Docker MCP Server is an MCP server that speaks that protocol over stdio and exposes your Docker host as a set of safe, richly‑described tools.
Point any MCP‑capable assistant at it and you can operate containers and Compose stacks in plain language — the model reads each tool’s schema, decides which to call, and reports the results back to you. No more memorising flags or copy‑pasting container IDs.
In one line: it’s the bridge between “I wish I could just tell my server what to do” and your actual Docker daemon.
💡 Why it exists
Day‑to‑day container work is a stream of small, repetitive commands:
docker ps -a
docker logs --tail 100 -f my-api
docker compose -f ./prod/compose.yaml up -d --build
docker stats my-api
Every one of those is trivial once you remember the exact syntax. The friction is the memorisation and the context‑switching. This server removes that friction by letting the AI do the translation, while keeping you in control through:
- Read‑only mode for safe demos and production insight.
- A container allowlist so the assistant can only touch what you allow.
- Opt‑in exec so arbitrary in‑container commands are never available by accident.
- Confirmation‑friendly design — destructive tools are clearly described so the model asks before it acts.
Built by SoyRage Agency for the self‑hosting and home‑lab community — and equally at home on a CI runner or a production VM behind read‑only mode.
🚀 Feature overview
🖥️ The interactive panel
Beyond the conversational interface, the project ships a minimalist web dashboard (docker-mcp-panel) for when you want a fast, visual, point‑and‑click view of your host. It reuses the exact same configuration, Docker client and safety rails as the MCP server — so read‑only mode and the allowlist apply here too.
npm run build
ragedocker panel # → http://127.0.0.1:4600 (or: npm run panel)
npm run panel:demo # same, but with realistic mock data (no daemon needed)
One command for everything. Since v1.1 a single
ragedockerlauncher fronts the whole toolkit — runragedockerwith no arguments for an interactive menu, or:ragedocker tui # the lazydocker-style terminal dashboard ragedocker panel # the web panel + monitoring API ragedocker mcp # the MCP server (Claude Desktop, Cursor, Continue…) ragedocker ia login # sign in to Claude or ChatGPT (see below) ragedocker doctor # check Docker, the AI and your configurationThe original
docker-mcp-tui/docker-mcp-panel/docker-mcp-serverbinaries still work as aliases.
🔑 AI copilot — sign in once with ragedocker ia login
The TUI copilot (press a) and the panel's AI terminal need a model. A short wizard sets one up — pick Claude (Anthropic, used natively) or ChatGPT (OpenAI), paste your key, and it's verified before saving:
ragedocker ia login # set up your main AI account
ragedocker ia secundaria # add a second account to switch to
ragedocker ia use secondary
ragedocker ia list # show what's configured (keys masked)
ragedocker ia test # call the model once and report back
Keys are stored at ~/.ragedocker/ai.json, owner‑readable only (0600), and are never echoed or logged. The legacy DOCKER_MCP_AI_* environment variables still take precedence for unattended deployments.
Dashboard — live host stats, containers & images
One‑click log tailing
Terminal — run docker commands with smart suggestions (Tab / ↑↓ / Enter)
Snapshots & scheduled backups — with email/cloud delivery
File explorer + editor — view & edit files inside a container
Browse a container's filesystem
System — networks & volumes
Alerts & log watch — with a live auto‑restart watchdog
Read‑only mode — actions safely disabled
Screenshots rendered in demo mode · watermarked © SoyRage Agency · soyrage.es
Panel highlights
- Tabbed layout — Overview, Terminal, Files, Backups, System and Alerts, with a live alert badge in the header.
- Live monitoring + Trends — CPU‑load and memory‑used cards with meters, per‑container CPU % and memory bars, and historical sparkline charts (sampled every 5s) for CPU and memory over time.
- ⌨️ AI‑powered terminal — type
docker …for typo‑tolerant, context‑aware completions (Tab/↑↓/Enter), or type a request in plain English (“why did web crash”) and pick Ask AI — the copilot proposes a command you review, then run. Commands are parsed to an argv array and spawned without a shell; a deny‑list blocks dangerous verbs and write verbs respect read‑only mode. AI uses any OpenAI‑compatible endpoint (OpenAI, Ollama, LM Studio…); without one it falls back to rule‑based suggestions. - 📁 File explorer + editor — browse any container's filesystem (breadcrumbs, up‑navigation), open and edit text/
.sh/config files, and Save back into the container. An AI edit button rewrites the file from a plain‑English instruction. Safe, shell‑freeexec; edits are blocked in read‑only mode. - 📸 Snapshots & scheduled backups — snapshot a container as an image (
commit) or a filesystemexport(.tar) to a chosen directory; schedule a daily backup (time, containers, type); a webhook forwards each backup to email, Google Drive or S3 via Zapier / Make / n8n. - 🧩 System tab — networks and volumes at a glance; per‑container inspect details (env redacted, mounts, ports, restart policy) in the drawer.
- ♻️ Auto‑restart watchdog — flip the Auto toggle and a background watchdog restarts a container whenever it exits (respects read‑only mode).
- 🚨 Alerts & log watch — down/unhealthy containers, high CPU/memory, watchdog events, and error/warn lines scanned from recent logs.
- Container grid — colour‑coded state dots, ports as chips, filter/search, auto‑refresh toggle, and per‑row actions (details · files · snapshot · start/stop/restart).
- — footer link exposes the scrape endpoint (see ).
Panel REST API (all local): /api/snapshot · /api/history · /api/containers · /api/images · /api/logs · /api/action · /api/run · /api/ai · /api/files · /api/file (GET read / POST save) · /api/inspect · /api/networks · /api/volumes · /api/backups · /api/backup · /api/schedule · /api/alerts · /api/autorestart · /metrics.
AI copilot (optional): set DOCKER_MCP_AI_ENDPOINT (+ DOCKER_MCP_AI_KEY, DOCKER_MCP_AI_MODEL) to power the AI terminal and AI file‑editing. Works with OpenAI, Ollama (http://localhost:11434/v1, free & local), LM Studio, or any OpenAI‑compatible API. Demo mode simulates it so you can try the UX offline.
🖼️ Regenerate the screenshots yourself with
npm run shots(requiresnpx playwright install chromium).
🔒 Panel security & networking (VPN, IPs, ports)
The panel and terminal can control your host, so treat access like SSH.
- Bind locally by default — the panel listens on
127.0.0.1:4600. Reach a remote host by tunnelling over a VPN — WireGuard or Tailscale — and browsing to the host's VPN IP. Do not port‑forward the panel to the public Internet. - If you must bind to the LAN, set
DOCKER_MCP_PANEL_HOST=0.0.0.0. On startup the server prints every IP address it is reachable on and a warning, e.g.:Panel ready at http://0.0.0.0:4600 reachable at http://127.0.0.1:4600 reachable at http://10.8.0.3:4600 ← your WireGuard IP reachable at http://192.168.1.42:4600 ← your LAN IP Panel is bound to ALL interfaces … keep it behind a VPN or an authenticated reverse proxy. - Change the port with
DOCKER_MCP_PANEL_PORT(e.g.8443) to avoid clashes or sit behind a reverse proxy. - Port‑forwarding / reverse proxy — if you expose it, put an authenticated proxy (Caddy/nginx/Traefik with Basic‑Auth or SSO + TLS) in front; never forward the raw port. Combine with
DOCKER_MCP_READONLY=truefor view‑only deployments, andDOCKER_MCP_PANEL_TERMINAL=falseto disable the command runner.
⌨️ The terminal UI (TUI)
Prefer the terminal? Launch docker-mcp-tui — a creative, lazydocker‑style dashboard that opens with a SoyRage Agency welcome and then drops you into a live, keyboard‑driven view. It’s hand‑rolled ANSI (no curses library), so it adds zero dependencies.
ragedocker tui # → interactive terminal dashboard (or: npm run tui)
npm run tui:demo # same, with realistic mock data (no daemon needed)
A warm welcome — “thank you for using our repository ⭐”
Live dashboard — gauges, details & one‑key actions
AI copilot — give an order in plain English
AI copilot. Press a (or :) to open the copilot bar and type what you want — “restart the web container”, “stop the backup job”, “show every container”. The copilot turns it into the exact docker command, shows it to you, and runs it only after you confirm with y. It speaks to any OpenAI‑compatible endpoint (DOCKER_MCP_AI_ENDPOINT / DOCKER_MCP_AI_KEY / DOCKER_MCP_AI_MODEL) and falls back to a built‑in rule engine in demo mode, so you can try it with zero setup.
Action menu. Press Enter (or m) over any container to open a menu of everything you can do to it — logs, inspect, shell, start/stop/restart, snapshot, restore, attach a volume, edit compose, copy id — arrow‑key navigable, so you never have to memorise a key. Every action also has a one‑key shortcut for power users.
Animated status. Containers no longer show a plain red/green dot: healthy ones breathe (●↔◉), starting/restarting ones spin (⠋⠙⠹…), unhealthy ones blink (▲), paused show ⏸, exited ○ — a glance across the list reads like a heartbeat monitor.
Keys: Enter/m menu · ↑/↓ (or j/k) navigate · g/G top/bottom · / filter · o sort (O reverse) · space pause live updates · l logs (f follow, +/- tail) · i inspect · e shell · c edit compose · y copy id · n/v/A networks/volumes/alerts · a AI · S/s/R lifecycle · b snapshot · B restore · V attach volume · u what's new · ? help · q quit.
Live CPU/memory gauges refresh automatically; the details pane shows lazydocker‑level info (health, uptime, command, restart policy, networks, mounts, env), lifecycle actions play a spinner animation, and read‑only mode hides the mutating keys (the copilot still explains, but never runs a mutating command).
Update notices. When a new version is published, both the TUI (a banner + u for the changelog) and the web panel (a dismissable banner) tell you — read from a single updates.json in the repo. It's silent on any failure and can be turned off with DOCKER_MCP_NO_UPDATE_CHECK=1.
📈 Monitoring: Prometheus, Zabbix & more
The panel doubles as a metrics exporter. It serves a standard Prometheus text endpoint at /metrics, so your Docker host becomes a first‑class monitoring target with no extra agent.
npm run panel # metrics on by default
curl http://127.0.0.1:4600/metrics
Exposed series (labelled by name, state, image where relevant):
Prometheus
# prometheus.yml
scrape_configs:
- job_name: docker-mcp
static_configs:
- targets: ["your-host:4600"]
Zabbix
Use an HTTP agent item pointed at http://your-host:4600/metrics, then add
dependent items with the Prometheus pattern preprocessing step, e.g.
dockermcp_containers_running or
dockermcp_container_cpu_percent{name="api"}. Grafana, Grafana Agent,
VictoriaMetrics and Netdata can scrape the same endpoint.
Turn the exporter off with
DOCKER_MCP_PANEL_METRICS=falseif you only want the UI.
🧩 Modular plugin architecture
The server is assembled from independent plugins, each owning one capability group. Which plugins load is driven entirely by configuration, so you can expose exactly the surface you want — from insight only to the full toolbox — without touching code. This also makes the project easy to extend.
🔒 The about plugin is locked — it carries the SoyRage Agency identity and cannot be disabled.
Toggle plugins via environment variables or the config file:
# Expose ONLY read-only insight (a safe, curated surface)
DOCKER_MCP_PLUGINS=containers,logs,images,system
# Load everything except container lifecycle
DOCKER_MCP_DISABLED_PLUGINS=lifecycle
Ask the assistant “list the plugins” any time to see what’s enabled.
Config file
For a reproducible setup, drop a docker-mcp.config.json in the project root (or point DOCKER_MCP_CONFIG at one). Environment variables always override it. See examples/docker-mcp.config.json:
{
"readOnly": false,
"allowExec": false,
"containerAllowlist": ["web", "api"],
"plugins": { "enabled": [], "disabled": ["lifecycle"] },
"panel": { "host": "127.0.0.1", "port": 4600, "demo": false }
}
Configuration precedence (lowest → highest): built‑in defaults → docker-mcp.config.json → .env → real environment variables.
🛠️ How it works
┌──────────────────────────────────────────────┐
You ◀──────▶ │ AI assistant (Claude / Cursor / Continue …) │
└───────────────────────┬──────────────────────┘
stdio · JSON‑RPC (MCP)
┌───────────────────────▼──────────────────────┐
│ Docker MCP Server │
│ │
│ 1. Client sends `initialize` → server │
│ replies with tool schemas + SoyRage │
│ `instructions` (identity & welcome). │
│ 2. Model picks a tool and sends `tools/call`.│
│ 3. Server executes it against Docker and │
│ returns human‑readable text. │
└───────────┬───────────────────────┬──────────┘
Engine API │ spawn │ docker compose
┌───────────▼───────────┐ ┌──────────▼──────────┐
│ Docker Engine │ │ Compose plugin │
└───────────────────────┘ └─────────────────────┘
- Engine operations (containers, images, stats, logs, system info) use the Docker Engine API through
dockerode. - Compose operations shell out to the official
docker composeCLI with a shell‑free, fully argument‑quoted spawn (no string interpolation, no injection surface). - stdout is sacred: it carries only the JSON‑RPC stream. Every log line goes to stderr.
✅ Requirements
📦 Installation
# 1. Clone
git clone https://github.com/<your-user>/docker-mcp-server.git
cd docker-mcp-server
# 2. Install dependencies
npm install
# 3. Build to dist/
npm run build
Kick the tyres with the official MCP Inspector (no AI client required):
npm run inspect
This opens a UI where you can list tools and call them by hand — perfect for verifying your Docker connection before wiring up an assistant.
🔌 Connecting to your AI client
Claude Desktop
Edit your Claude Desktop config file:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"docker": {
"command": "npx",
"args": ["-y", "@soyrageagency/docker-mcp"],
"env": {
"DOCKER_MCP_READONLY": "false",
"DOCKER_MCP_ALLOW_EXEC": "false",
"DOCKER_MCP_DEFAULT_LOG_TAIL": "200"
}
}
}
}
A ready‑to‑edit copy lives in
examples/claude_desktop_config.json.
No install step needed: npx fetches the package on first run and keeps it up to date. Restart Claude Desktop and ask: “What containers are running?”
Cursor / Continue / Zed
Any MCP‑capable client works the same way — register a stdio server whose command is npx with the arguments -y @soyrageagency/docker-mcp, passing the same environment variables. Consult your client’s MCP documentation for the exact config location; the server block is identical.
🌐 Run it over the network (HTTP)
By default an MCP server talks over stdio: your AI client starts a copy of it as a child process, on your machine. That is fine for a laptop tool and awkward for a homelab, where the Docker daemon lives on a server — and where you probably want your desktop and your laptop talking to the same thing.
Set one variable and it serves Streamable HTTP instead:
DOCKER_MCP_HTTP=true DOCKER_MCP_HTTP_TOKEN="$(openssl rand -hex 32)" npx -y @soyrageagency/docker-mcp
Then point any MCP client at it:
{
"mcpServers": {
"docker": {
"type": "http",
"url": "http://10.0.0.5:8620/mcp",
"headers": { "Authorization": "Bearer <the token you generated>" }
}
}
}
Read this before you expose it. The Docker socket is root on your host, so
anyone who can reach this port can do anything to it. It binds loopback by
default and warns loudly if you start it without a token. Put it behind your
VPN, and consider pairing it with DOCKER_MCP_READONLY=true or a container
allowlist for anything you do not fully trust.
There is also GET /health, which needs no token, for container healthchecks.
🩺 Diagnostics
Three read-only tools aimed at the questions you actually ask, rather than at the API surface:
host_health — one call that answers is anything wrong? Failing
healthchecks, containers crash-looping, containers that are down despite a
restart policy (the failure nobody notices), and disk pressure from
reclaimable images and volumes. Findings ranked by severity, not a data dump.
find_restart_loops — the containers that keep dying, with the exit code
and the tail of their logs, which is where the reason almost always is. It
saves the usual ps → inspect → logs round trip that takes three messages.
find_unused_resources — what is safe to clean and what it would return,
split into images, volumes and long-dead containers. It refuses to be glib
about volumes: an unreferenced volume is very often the database of a stack you
stopped on purpose, and docker volume prune is not undoable.
All three are read-only, so they stay available with DOCKER_MCP_READONLY=true.
💬 Guided workflows (prompts & resources)
Tools only answer a question you already knew how to ask. MCP prompts are the other half: your client lists them, so the workflow is discoverable without knowing which tool to reach for or in what order.
Each prompt also tells the assistant what a good answer looks like: verdict first, findings ranked, no padding, and an explicit instruction not to change anything.
Resources expose the host as attachable context, so the model can be handed the current picture instead of spending three tool calls rebuilding it:
docker://host/overview— containers, images and disk usage in one snapshot.docker://server/capabilities— which plugins are loaded, whether the server is read-only, whether exec is allowed, and what the allowlist permits.
⚙️ Configuration reference
Every setting is an environment variable. A local .env file (next to package.json) is loaded automatically at startup; values already present in the process environment always win, so your MCP client can override the file. See .env.example for a commented template.
Boolean parsing: any of 1, true, yes, on (case‑insensitive) counts as true. A JSON config file provides defaults for all of the above — see Config file.
🌐 Connecting to remote / TLS daemons
Manage a Docker host over the network by pointing DOCKER_HOST at its TCP endpoint. For anything beyond localhost, always use TLS.
# Plain TCP (trusted networks only!)
DOCKER_HOST=tcp://192.168.1.50:2375
# Secured TCP with mutual TLS
DOCKER_HOST=tcp://docker.internal:2376
DOCKER_TLS_VERIFY=1
DOCKER_CERT_PATH=/home/you/.docker/certs
When TLS is enabled the server reads ca.pem, cert.pem and key.pem from DOCKER_CERT_PATH and connects over HTTPS (default port 2376; plain TCP defaults to 2375).
🛡️ Security model
This server can control your infrastructure, so it ships with defence‑in‑depth defaults. You decide how much power to grant.
Safety recipes
# Give a live demo with zero risk of mutation
DOCKER_MCP_READONLY=true
# Let the AI manage only the app tier, never data stores
DOCKER_MCP_CONTAINER_ALLOWLIST=web,api,worker
# Never allow shelling into containers (this is the default)
DOCKER_MCP_ALLOW_EXEC=false
⚠️ Principle of least privilege. Start read‑only, add an allowlist, and only enable writes/exec once you trust the setup. Treat the assistant as a very fast junior engineer: helpful, but you sign off on the destructive stuff.
🧰 Complete tool reference
Tools marked W change state and are hidden when DOCKER_MCP_READONLY=true.
exec_in_container is additionally hidden unless DOCKER_MCP_ALLOW_EXEC=true.
Identity
Insight (read‑only)
Compose — read‑only
Lifecycle (W)
Compose — state‑changing (W)
💬 Example conversations
Natural‑language prompts and the tools the model will typically reach for:
Want a stack to practise on? examples/demo-stack/compose.yaml spins up nginx + redis. Try: “Deploy the demo stack, then show me its services and the web logs.”
🗂️ Project structure
docker-mcp-server/
├── assets/
│ ├── soyrage-banner.svg # SoyRage Agency identity banner (this README)
│ └── screenshots/ # Watermarked panel screenshots
├── examples/
│ ├── claude_desktop_config.json
│ ├── docker-mcp.config.json # Reproducible config-file example
│ └── demo-stack/
│ └── compose.yaml # nginx + redis playground
├── install.sh / install.ps1 # One-command bootstrap for beginners
├── scripts/
│ ├── install.mjs # Cross-platform Claude Desktop configurator
│ ├── copy-public.mjs # Copies panel assets into dist/ after build
│ ├── shots.mjs # Regenerates the panel screenshots (Playwright)
│ └── tui-shot.mjs # Renders the TUI to PNG (ANSI→HTML→Playwright)
├── src/
│ ├── index.ts # MCP entry point: banner, wiring
│ ├── branding.ts # SoyRage identity, ASCII banner, MCP instructions
│ ├── plugins.ts # Modular plugin catalogue & selection loader
│ ├── config.ts # Layered config (defaults → file → .env → env)
│ ├── logger.ts # stderr‑only structured logger (stdout is sacred)
│ ├── docker/
│ │ ├── client.ts # Typed dockerode wrapper + allowlist enforcement
│ │ └── compose.ts # Safe, shell‑free `docker compose` driver
│ ├── tools/ # One module per plugin's tools
│ │ ├── context.ts # Shared dependency bundle + plugin metadata
│ │ ├── about.ts # about / list_plugins (identity, locked)
│ │ ├── containers.ts # list / inspect / stats
│ │ ├── logs.ts # log tailing with stream demultiplexing
│ │ ├── lifecycle.ts # start / stop / restart / remove / exec
│ │ ├── images.ts # image inventory
│ │ ├── system.ts # system_info / disk_usage / networks / volumes
│ │ └── compose.ts # deploy / down / restart / pull / ps / config
│ ├── panel/ # Interactive web dashboard
│ │ ├── index.ts # Panel entry point (docker-mcp-panel binary)
│ │ ├── server.ts # Node‑core HTTP server + REST API + /metrics
│ │ ├── service.ts # UI/monitoring data layer, stats & Prometheus
│ │ └── public/ # Hand‑written SPA (index.html, styles.css, app.js)
│ ├── tui/ # Terminal UI (docker-mcp-tui binary)
│ │ ├── index.ts # TUI entry point (+ --frame/--splash snapshots)
│ │ ├── app.ts # Interactive app: welcome, gauges, key handling
│ │ ├── box.ts # Rounded box renderer
│ │ └── ansi.ts # ANSI colours, cursor control, width-aware pads
│ └── utils/
│ ├── format.ts # tables, byte & time humanisers
│ └── result.ts # MCP result helpers + error guard
├── docker-mcp.config.json # (optional) your config file
├── .env.example # Commented configuration template
├── LICENSE # MIT License
└── README.md
🧠 Design principles
- stdout is reserved for the JSON‑RPC protocol stream; every diagnostic goes to stderr. Violating this corrupts the MCP connection — the logger enforces it.
- No shell interpolation. Compose commands are spawned with an argument array, never a shell string, eliminating command‑injection risk.
- Fail soft. A handler that throws returns a clean
isErrortext result the model can read and recover from, instead of tearing down the transport. - One concern per module. Tools are grouped by capability; each group is a small, focused file that receives its dependencies explicitly (no globals).
- Tiny dependency surface. A hand‑rolled
.envloader keepsdotenvout; only@modelcontextprotocol/sdk,dockerodeandzodare runtime dependencies. - Safety by construction. Read‑only mode and the allowlist are checked at the boundary, so an unsafe call can’t slip through a forgotten branch.
🧪 Development
npm run dev # hot‑reload the MCP server with tsx
npm run typecheck # strict type check, no emit
npm run build # compile to dist/ and copy panel assets
npm run start # run the built MCP server
npm run inspect # launch the MCP Inspector against the built server
npm run panel # run the interactive panel (with /metrics)
npm run panel:dev # hot‑reload the panel with tsx
npm run panel:demo # run the panel with demo data
npm run tui # run the terminal UI
npm run tui:demo # run the terminal UI with demo data
npm run shots # regenerate panel screenshots (needs Playwright chromium)
npm run clean # remove dist/
Coding standards: TypeScript strict with noUnusedLocals, noUnusedParameters, noImplicitReturns and noFallthroughCasesInSwitch.
Continuous integration: .github/workflows/ci.yml runs on every push/PR — install, type‑check, build, then the deep end‑to‑end suite (node scripts/deep-test.mjs, 70 checks) against a headless demo panel. Run it locally anytime:
npm run build
DOCKER_MCP_PANEL_DEMO=true DOCKER_MCP_PANEL_PORT=4600 node dist/panel/index.js &
node scripts/deep-test.mjs
🩺 Troubleshooting & FAQ
The server started but couldn’t connect to Docker. Check that:
- Docker Desktop / the daemon is running.
DOCKER_HOSTis correct for your platform (empty = default socket).- On Linux, your user can access the socket (
dockergroup) or you’re running with sufficient permissions.
The server intentionally keeps running so tool calls return a friendly error inside your chat client instead of crashing.
The Compose tools shell out to docker compose. Install Docker Desktop or the docker-compose-plugin, and make sure docker is on the PATH of the environment your MCP client launches the server in.
You’re probably in read‑only mode. Set DOCKER_MCP_READONLY=false (the default) and restart your MCP client so it re‑reads the tool list.
DOCKER_MCP_CONTAINER_ALLOWLIST is set and the target doesn’t match. Add its name/prefix to the list, or clear the variable to allow all.
No. This server talks only to your Docker daemon and your MCP client over local stdio. It makes no outbound network calls of its own.
🗺️ Roadmap
The full roadmap — what is shipped, what is next, and what is deliberately not planned — lives in ROADMAP.md.
The short version: a multi-arch ghcr.io image and a socket-proxy recipe, then
finer-grained permissions than the current read-only/read-write switch. Image
update checking and metrics history are further out because doing them badly
means confidently wrong answers.
Explicitly not planned: replacing Portainer, autonomous action without confirmation, and telemetry of any kind.
🤝 Contributing
Contributions are welcome! Please:
- Open an issue describing the change before large PRs.
- Keep the stderr‑only logging and shell‑free Compose invariants intact.
- Run
npm run typecheck && npm run buildbefore submitting.
🏢 About SoyRage Agency
SoyRage Agency is a full‑stack development & infrastructure studio based in Valencia, Spain, building tools where DevOps meets AI. We craft polished, production‑minded software for developers and the self‑hosting community.
- 🌐 Web: soyrage.es
- 🧑💻 Focus: full‑stack development · infrastructure engineering · AI tooling
- 📫 Work with us: soyrage.es
If this project is useful to you, a ⭐ on the repo and a link back to soyrage.es genuinely help us keep building in the open. Thank you! 🙌
🧰 More from the SoyRage self‑hosting suite
Docker MCP Server is part of a family of open‑source infrastructure tools built with the same care — same design language, same safety‑first defaults, same "chat with your infra" philosophy:
💙 Support the project
Docker MCP Server is free and MIT licensed. If it saves you time, you can support development on PayPal — a ⭐ on the repo helps just as much.
🖋️ Credits & License
Designed, built and maintained by SoyRage Agency — https://soyrage.es/
Released under the MIT License — use it, modify it, self-host it, ship it commercially.
If you build something on top of it, a link back to soyrage.es is appreciated but never required.
© 2026 SoyRage Agency — https://soyrage.es/
Made with ❤ in Valencia, Spain.
