Lifecycle, images, networks and volumes are all reachable from one connection, so an investigation that starts with "why is this container restarting" can go all the way to reading its logs and running a command inside it without a terminal.
A Docker management server covering twenty-two operations across the four Docker object types. It talks to the Docker Engine on the machine it runs on, with that machine's Docker permissions.
- Containers listed, created, run, started, stopped, recreated and removed, with logs fetched on demand
- Commands executed inside a running container, and files copied from the host into one
- Images listed, built, pulled, tagged, pushed and removed
- Networks and volumes listed, created and removed
- Running and stopped containers both in the listing, so a container that exited is still visible
Ruby 3.2 or newer, the gem installed, a running Docker Engine, and Docker permissions for the user the server runs as. Two of the tools reach outside the container boundary — one executes arbitrary commands inside a container, the other copies host files in — so the authors recommend restricted Docker permissions and a trusted environment rather than exposure to an untrusted client.
One command — gem install docker_mcp