Server facts
docker-mcp
Project
- Author
- GavinLucas
- Repository
- github.com/GavinLucas/docker-mcp
- License
- Not specified
- Category
- Cloud & DevOps
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 9
- Last commit
- Data as of
Tags
- Devops
- Python
- compose
- containers
- docker
- sdk
- swarm
Overview
Docker image preparation and Compose service management form connected workflows in docker-mcp. Agents can inspect registry tags, manifests, and image configuration without downloading images, then build through the classic builder or Buildx. Buildx tools cover platform targeting, cache handling, attestations, and build history inspection. Compose tools let agents fetch images before startup, render merged configuration, launch services, check their status, and retrieve logs. Separate operations support restarting existing services, executing tasks inside running containers, and moving files between containers and the server host. Docker Scout tools add vulnerability reports, image comparisons, and base-image upgrade suggestions.
For operational investigation, container inspection, resource snapshots, process listings, events, and disk-usage reports provide evidence about failures or resource pressure. Swarm tools extend administration to stacks, service scaling and rollback, nodes, secrets, and configuration objects. Developers and operators can connect agents to the local Docker socket or configure several daemons, including remote endpoints using TCP, TLS, or SSH. Individual daemons can be designated read-only; server-wide read-only and no-destructive modes restrict which tools are registered. Tool domains can also be excluded to shorten the exposed tool list.
docker-mcp setup notes
- docker-mcp records stdio only; confirm a network transport upstream before planning remote access.
- docker-mcp has no recorded license; confirm reuse terms in its repository.