docker-mcp
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-containerC | Create a new standalone Docker container |
| deploy-composeC | Deploy a Docker Compose stack |
| get-logsC | Retrieve the latest logs for a specified Docker container |
| list-containersB | List all Docker containers |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| deploy-stack | Generate and deploy a Docker stack based on requirements |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: create-container for creating containers, deploy-compose for deploying stacks, get-logs for retrieving logs, and list-containers for listing containers. The descriptions make it easy to tell them apart.
All tool names follow a consistent verb_noun pattern (e.g., create-container, deploy-compose, get-logs, list-containers). There are no deviations in naming style or conventions.
With 4 tools, the count is reasonable for a Docker MCP server, covering key operations like creating, listing, and managing containers and stacks. It's slightly lean but well-scoped for basic Docker management tasks.
The toolset covers core operations (create, list, logs, deploy) but has notable gaps, such as missing update, delete, or stop/start container tools, which could limit agent workflows for full container lifecycle management.