Docker MCP Server
Related Servers
Alternatives to Docker MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceAn MCP server that gives LLMs direct control over a local Docker daemon, enabling container, image, volume, network, and Compose stack management through natural language.234-
- AlicenseBqualityFmaintenanceA powerful Model Context Protocol (MCP) server for Docker operations, enabling seamless container and compose stack management through Claude AI.4501MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Podman and Docker container runtimes, enabling management of containers, images, networks, and volumes via AI assistants.81Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables LLMs to run ANY code safely in isolated Docker containers.121MIT
- FlicenseAqualityFmaintenanceA Model Context Protocol server that enables Docker container management through natural language interactions using a custom GPT interface.715-
- AlicenseNot gradedqualityCmaintenanceUniversal MCP server that wraps any CLI tool, enabling AI assistants to run commands via natural language.MIT
TDQS
Scored across 10 tools
Each tool maps to a distinct area: read vs control for containers and compose, db query vs db admin, plus exec, logs, health, and resource inspection. Cross-references in descriptions actively prevent misselection, and even tools with multiple sub-actions keep their scope clearly separated.
All names use the docker_ prefix and snake_case, with a predictable pattern: base nouns for read/inspect tools, _control for lifecycle actions, and _admin for database maintenance. The container, compose, and db families all follow the same naming convention.
Ten tools is well within the ideal range and matches the server's breadth: container/compose control, exec, logs, database operations, health, and resource inspection. There is no redundant tool or unnecessary bloat.
The set covers the core Docker Compose workflow: inspect config, up/down stacks, control services, exec, logs, database query/backup/restore, health, and resource listing. Missing standalone container create/remove or image build/pull are plausible gaps, but the described Compose-focused scope has no glaring dead ends.