官方说明7 个来源MCP 服务8 天前

friendlygeorge/docker-mcp-server

Docker MCP server designed for agents that need their containers to stay running. Health checks, auto-restart, Compose lifecycle, log streaming.

在 GitHub 查看 ↗直链 · 无中转页

配置模板（请按你的客户端调整）

claude mcp add docker-mcp-server -- npx -y docker-mcp-server

这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。

★ 数取值: 4 ★ · friendlygeorge/docker-mcp-server · 取自该仓库的 GitHub 页面 · （2026-10-16 20:00:20 核对）
来源明细: 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
收录与活跃: 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
评分构成: 综合分 703 · 4 ★ · 7 个来源 · mcp

常见问题（答案都来自我们的记录）

怎么安装？

我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。

它适合谁 / 用来做什么？

我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。

谁维护它、还在更新吗？

仓库 friendlygeorge/docker-mcp-server；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。

第三方质量标记

@supernova123/docker-mcp-server

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

**The Docker MCP server designed for agents that need their containers to stay running.**
> **Runs locally. No API keys. No paid plan.** Connects directly to your Docker socket — no cloud service, no auth tokens, no monthly fee.
>
> **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 |
| **Runs locally** | ✅ No API keys, no paid plan | ✅ | ❌ Requires Docker Hub auth |
| **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 |
| **Fleet monitoring** | ✅ 6 fleet tools (status, stats, events, logs, thresholds, dashboard) | ❌ | ❌ |
| **Agent positioning** | ✅ Built for agents | Generic Docker | Registry API |
Use Cases
**Agent-managed deployments:** Your agent deploys a new version, checks health, waits for readiness, then switches traffic. If the health check fails, it auto-rolls back.
**Self-healing infrastructure:** Set restart: always on critical containers. Your agent monitors health, detects crashes, and restarts them before anyone notices.
**Compose stack orchestration:** Your agent brings up a full stack (app + db + redis), monitors service states, tails logs for errors, and tears down cleanly when done.
**Debugging sessions:** Your agent execs into a container, runs diagnostics, streams logs with timestamp filters, and captures stats — all without SSH.
How It Works
Here's what an agent actually does with this server during a deployment:
If the health check fails at step 2, your agent catches it immediately — no 3am alerts, no user complaints. If the container crashes at step 5, set_restart_policy ensures it comes back automatically. The agent doesn't just deploy containers — it keeps them running.
Blog Posts
Real data from building and running this server:
- I Cut My Docker MCP Server From 50 to 12 Tools — why fewer tools = better agent UX