docker-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCKER_HOST | No | Docker daemon address (e.g., ssh://user@host, tcp://host:2376). Default: local socket /var/run/docker.sock | |
| DOCKER_CERT_PATH | No | Path to TLS certificate directory (e.g., ~/.docker/certs) | |
| DOCKER_TLS_VERIFY | No | Enable TLS verification (set to '1' to enable) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docker_pingA | Check connectivity to the Docker daemon and return version/diagnostics. |
| container_queryC | List or inspect Docker containers. |
| container_actionB | Start, stop, restart, pause, unpause, or remove a container. |
| container_createB | Create a new container from an image. |
| container_logsB | Get container logs. ANSI codes stripped, capped at max tail. |
| container_execA | Run a command in a running container. Output capped at 200 lines / 10KB. |
| image_queryA | Query Docker images: list all images or inspect a specific image by name or ID. |
| image_actionB | Perform actions on Docker images: pull, remove, tag, or push. |
| image_buildB | Build a Docker image from a context (tar file path) and optional Dockerfile. |
| volume_queryB | List or inspect Docker volumes. |
| volume_actionB | Create or remove a Docker volume. |
| network_queryC | List or inspect Docker networks. |
| network_actionC | Create, remove, connect, or disconnect a Docker network. |
| compose_actionA | Run a docker compose lifecycle action (up, down, pull, stop) against a compose project file. Uses the local Docker socket. |
| compose_queryA | Query docker compose state: "ps" (container status), "config" (resolved compose config), or "logs" (service log tail). |
| system_dfA | Return Docker disk usage: breakdown by containers, images, volumes, and build cache. Output is already compact — shipped raw. |
| system_pruneA | Prune unused Docker resources by scope and return a summary of reclaimed space. Use scope "all" to prune every category and aggregate reclaimed bytes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool targets a distinct resource (compose, container, image, network, system, volume) and action (action, query, create, etc.), with no overlaps. Even similar verbs like 'action' and 'query' are clearly separated by resource type.
Tool names follow a consistent snake_case pattern: resource_action (e.g., container_create, image_build, network_query). The only exception is 'docker_ping', but it still follows the convention of prefixing with the resource name.
17 tools is appropriate given Docker's broad domain, covering containers, images, networks, volumes, compose, and system operations. Each tool serves a distinct purpose without unnecessary bloat.
The tool set covers core CRUD and lifecycle operations for all major Docker resources, including compose. Minor gaps exist (e.g., container commit, stats, login), but the surface is sufficient for most common workflows.