dockerbro
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCKER_HOST | No | Docker daemon endpoint to connect to (e.g., tcp://192.168.1.50:2375). | |
| DOCKER_MCP_LOG | No | Path to a log file for DockerBro. | |
| DOCKER_MCP_DENY_TOOLS | No | Comma-separated denylist of tools that are always blocked. | |
| DOCKER_MCP_ALLOW_TOOLS | No | Comma-separated allowlist of tools that are exposed and callable. |
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 |
|---|---|
| list_containersA | List Docker containers with status, image, ports. |
| inspect_containerC | Get detailed info about a container. |
| start_containerA | Start a stopped container. |
| stop_containerC | Stop a running container. |
| restart_containerC | Restart a container. |
| remove_containerA | Remove a stopped container. Pass force=true for running containers. |
| logs_containerB | Get recent log output from a container. |
| exec_containerB | Execute a command inside a running container. |
| list_imagesA | List Docker images on the local system. |
| pull_imageB | Pull a Docker image from a registry. |
| run_containerB | Run a new container from an image. |
| remove_imageB | Remove a Docker image. |
| docker_compose_psB | List Docker Compose services. |
| docker_compose_upB | Start Docker Compose services. |
| docker_compose_downA | Stop and remove Docker Compose services. |
| docker_compose_logsC | Get Docker Compose service logs. |
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 16 tools
Each tool targets a distinct Docker resource and action. Container management tools (list, inspect, start, stop, restart, remove, logs, exec, run) are clearly separated from image tools (list, pull, remove) and compose tools (up, down, logs, ps). No two tools have overlapping purposes.
Most tools follow a verb_noun pattern (e.g., list_containers, start_container, remove_image). The Docker Compose tools consistently use a docker_compose_ prefix with a verb suffix, which is a slight deviation from the main pattern but remains predictable and internally consistent.
With 16 tools, the server is well-scoped for Docker management. Each tool covers a distinct operation, and the count is appropriate for handling containers, images, and Compose workflows without being overwhelming or sparse.
The tool set covers the core Docker lifecycle: container run/start/stop/restart/remove/logs/exec, image list/pull/remove, and Compose up/down/logs/ps. Missing operations like image build/push or container stats are notable but not critical for common workflows, allowing agents to work around the gaps.