Docker
Give your agent structured JSON from Docker ps, images, logs, and builds so you can debug containers without memorizing every CLI flag.
Overview
io.github.Dave-London/docker is an Operate-phase MCP server that returns typed JSON from Docker ps, images, logs, and build commands for agents.
What is this MCP server?
- Exposes docker ps, images, logs, and build as typed JSON MCP tools
- Helps agents answer “what is running?” and “why did this container exit?” from chat
- stdio transport on @paretools/docker npm package (v0.8.0)
- Useful for solo SaaS on Compose, Fly, or self-hosted VPS stacks
- Complements Pare git and build servers for ship-and-operate workflows
- Server version 0.8.0
- npm identifier @paretools/docker
- Documented tool surface: ps, images, logs, and build operations
Community signal: 128 GitHub stars.
What problem does it solve?
Container state and logs are painful to paste into chat, so indie operators waste time manually summarizing what Docker already knows.
Who is it for?
Solo builders who dockerize side projects and want MCP-driven visibility into local or single-server container fleets from Claude Code or Cursor.
Skip if: Kubernetes-only teams that never touch the Docker CLI, or builders without Docker daemon access on the configured machine.
What do I get? / Deliverables
Your agent can query running containers, images, and logs as JSON and help you fix compose files, Dockerfiles, and runtime failures faster.
- Structured JSON for container status, images, and log excerpts
- Agent-assistable docker build feedback for image iteration
Recommended MCP Servers
Journey fit
Listing containers, tailing logs, and inspecting images are day-two production and local infra tasks—Operate, not first ideation. Docker ps, logs, and image management are infrastructure hygiene for anything you already ship in containers.
How it compares
Docker CLI MCP adapter, not a hosted PaaS dashboard and not a security audit skill.
Common Questions / FAQ
Who is io.github.Dave-London/docker for?
Indie developers and tiny teams using Docker for apps or local dev stacks who want their coding agent to inspect containers and logs via structured tools.
When should I use io.github.Dave-London/docker?
Use it when a service fails after deploy or during local compose runs and you need ps, logs, images, or rebuild context inside the agent session.
How do I add io.github.Dave-London/docker to my agent?
Install @paretools/docker, add the stdio MCP server to your client, ensure the Docker CLI and daemon are reachable for the user running the agent, then grant only the access you are comfortable automating.