Docker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_containersC | List all Docker containers |
| list_imagesC | List Docker images |
| create_containerC | Create a new Docker container |
| run_containerB | Run a container (create and start). This is the preferred method for starting containers. |
| start_containerB | Start a stopped Docker container |
| stop_containerC | Stop a running Docker container |
| remove_containerC | Remove a Docker container |
| inspect_containerC | Get detailed information about a container |
| container_logsC | Get logs from a container |
| pull_imageC | Pull a Docker image from a registry |
| list_networksB | List Docker networks |
| list_volumesB | List Docker volumes |
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 12 tools
Every tool has a clearly distinct purpose targeting specific Docker resources and actions. For example, create_container and run_container are well-differentiated by their descriptions, with run_container explicitly noted as the preferred method for starting containers. There is no ambiguity or overlap in functionality across the tool set.
All tool names follow a consistent verb_noun pattern using snake_case, such as list_containers, create_container, and stop_container. This predictable naming convention makes it easy for agents to understand and select the appropriate tools without confusion.
With 12 tools, the server is well-scoped for managing Docker containers, images, networks, and volumes. Each tool earns its place by covering essential operations like creation, listing, starting, stopping, and removal, without being overly sparse or bloated.
The tool set provides strong coverage for core Docker operations, including CRUD for containers and listing for other resources. Minor gaps exist, such as no tools for creating or removing networks/volumes, but agents can still perform most workflows effectively with the available tools.