{"id":"makbn-docker-mcp-server","name":"docker_mcp_server","af_score":49.5,"security_score":40.5,"reliability_score":25.0,"what_it_does":"Provides a Model Context Protocol (MCP) server that exposes Docker Engine and Docker Swarm operations as MCP Tools, using the mcp_mediator framework to auto-generate tool interfaces from Docker client methods (optionally with @McpTool annotations).","best_when":"You have an MCP-capable client (e.g., Claude Desktop) running locally or in a controlled network and you want the agent to perform Docker/Swarms tasks by calling well-named MCP tools.","avoid_when":"You cannot restrict the Docker host permissions or you need robust safeguards against data exfiltration (logs/files via copy/logs/exec) and destructive operations (remove/prune/kill).","last_evaluated":"2026-04-04T20:02:54.885914+00:00","has_mcp":true,"has_api":false,"auth_methods":["Docker Engine API authentication via TLS client certificates (tcp:// with --tls-verify and --cert-path).","Docker registry auth for pull/push/auth tools (reported as supported; exact method not specified in README)."],"has_free_tier":false,"known_gotchas":["Destructive commands are exposed as tools (remove/kill/prune/leave/swarm operations), so an agent needs strict guardrails/allowlists.","The MCP tool interface is largely auto-generated; tool parameter naming/types and edge-case behavior may require inspecting the underlying DockerClientService and DockerMcpServer implementation.","Many commands interact with the Docker daemon and may fail due to permissions, daemon availability, or TLS/cert configuration; README does not document expected error formats or recovery patterns.","Operations that transfer data (docker_copy_archive_to_container/from_container, docker_log_container/service, docker_exec_command) can enable sensitive data exposure unless constrained."],"error_quality":0.0}