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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docker_remote_connectionC | Connect to remote Docker hosts via SSH or configure Docker host |
| docker_backup_migrationC | Backup containers, volumes, and entire projects for migration |
| docker_monitoring_advancedC | Enhanced monitoring with health checks, events, and detailed statistics |
| docker_compose_advancedB | Manage Docker projects with natural language using plan+apply workflow |
| execute_docker_commandC | Execute Docker commands using natural language or direct commands |
| manage_containersC | Manage Docker containers (list, start, stop, remove) |
| manage_imagesC | Manage Docker images (list, pull, remove, build) |
| docker_infoC | Get Docker system information and statistics |
| manage_volumesC | Manage Docker volumes (list, create, remove, inspect) |
| manage_networksC | Manage Docker networks (list, create, remove, inspect, connect, disconnect) |
| create_containerC | Create and run Docker containers with advanced options |
| docker_registryC | Search Docker Hub, login/logout, push/pull operations |
| docker_monitoringC | Monitor containers, get logs, inspect resources, and troubleshoot issues |
| docker_composeC | Manage Docker Compose services |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docker-help | Comprehensive Docker commands and natural language examples |
TDQS
Scored across 14 tools
There is significant functional overlap between tools, particularly in monitoring and management areas. For example, 'docker_monitoring' and 'docker_monitoring_advanced' have unclear boundaries, and 'manage_containers' overlaps with 'create_container' and potentially 'docker_compose' operations. While descriptions provide some differentiation, agents may struggle to choose between these tools for common tasks.
Most tools follow a consistent snake_case pattern with descriptive names, but there are notable deviations. 'docker_backup_migration' uses an underscore instead of a verb, and 'execute_docker_command' has a different structure than the majority. The naming is generally readable but lacks complete uniformity across all tools.
With 14 tools, the count is reasonable for Docker management, covering a broad scope from containers to images, networks, volumes, and system operations. However, some tools feel redundant (e.g., two monitoring tools), suggesting the set could be more streamlined without losing functionality for the domain.
The tool set provides comprehensive coverage of Docker operations, including CRUD for containers, images, networks, and volumes, plus monitoring, registry interactions, remote connections, and system info. There are no obvious gaps; agents can perform end-to-end workflows from setup to maintenance and troubleshooting in this domain.