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 |
|---|---|
| docker_runC | Запустить Docker контейнер |
| docker_psA | Получить список контейнеров |
| docker_stopC | Остановить контейнер |
| docker_removeB | Удалить контейнер |
| docker_logsA | Получить логи контейнера |
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 5 tools
Each tool addresses a distinct container lifecycle action: run, list, stop, remove, and logs. There is no overlap in purpose, making tool selection unambiguous.
All tools follow a consistent docker_verb naming pattern, using lowercase snake_case. This predictability aids agent comprehension and usage.
With exactly 5 tools, the server is well-scoped for basic Docker container management. Each tool covers an essential operation without redundancy.
The core container lifecycle (create/run, list, stop, remove, logs) is covered. A notable gap is the lack of a start command for stopped containers, but this can be worked around by running a new container.