docker-logs-mcp
Related Servers
Alternatives to docker-logs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for monitoring and managing long-running processes on a remote VPS via SSH, with tools for status, logs, record summaries, and arbitrary command execution.12 npmMIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server for inspecting and operating Linux VPS deployments through restricted SSH.2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for managing VPS servers via SSH, enabling command execution, file transfer, Docker management, and server documentation from within Claude.8 npmISC
- FlicenseBqualityDmaintenanceA log analysis MCP server that enables tailing, searching, filtering, and summarizing logs from local files and Docker containers.7-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that gives any LLM client the ability to list, inspect, start, stop, and monitor Docker containers on the host machine.1-
- AlicenseBqualityDmaintenanceAn MCP server for managing and monitoring Docker, Docker Compose, and Kubernetes environments alongside Azure Application Insights. It enables advanced log filtering, container lifecycle management, and querying of cloud application traces and metrics.7MIT
TDQS
Scored across 5 tools
Most tools are distinct: docker_ps, docker_stats, and server_info each serve clear different purposes. docker_logs and docker_grep both deal with logs, but their descriptions clearly separate recent-error viewing from pattern searching, so ambiguity is mild.
Four tools use the consistent 'docker_' prefix and short noun pattern (docker_logs, docker_ps, docker_grep, docker_stats). server_info breaks the pattern by not using the 'docker_' prefix, creating a minor inconsistency.
With five tools, the set is well-scoped for a Docker log and monitoring server. Each tool covers a distinct need without redundancy or unnecessary bloat.
The set covers the core domain: viewing logs, searching logs, listing containers, checking resource usage, and overall server health. Minor gaps might include container lifecycle actions, but those are outside the apparent logging/monitoring purpose.