Docker

Not an official Docker Inc. project — this is a community server by ckreiling that talks to the local Docker socket (or a remote daemon over TLS) using the docker-py SDK. The go-to option for giving an agent hands-on container control without exposing a full shell. What it does: - Container run, stop, start, restart, and log tailing - Image pull, build from a Dockerfile, tag, push, and prune - Compose up, down, and ps against a specified project directory - Volume and network list, create, and remove - Streams stdout and stderr back as MCP progress notifications during long operations - Works against a local socket or a remote daemon via DOCKER_HOST Example: Launch with the socket mounted. An agent can build a service's image from its Dockerfile, run the container with environment overrides, inspect logs, then tear it down — all inside a single conversation, useful for quick reproducers of CI failures. Setup: Default config uses /var/run/docker.sock on Linux and macOS, or the named pipe on Windows. Override DOCKER_HOST (tcp://... or ssh://...) to target a remote daemon. Transport: stdio. Install via "uvx mcp-server-docker" for an isolated Python environment. Notes: Grant socket access deliberately. A process with /var/run/docker.sock mounted is root-equivalent on the host — it can spawn privileged containers, mount arbitrary host paths, and pivot out of any weaker sandbox. For shared environments use a remote daemon behind mTLS, not the local socket. Single-maintainer project; pin a version and test upgrades rather than tracking latest.