OPS MCP Server
Related Servers
Alternatives to OPS MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceEnables managing Linux servers via SSH with tools for command execution, file operations, service management, and log analysis.-
- AlicenseBqualityDmaintenanceEnables SSH connectivity and remote command execution on servers, allowing users to test connections and run commands remotely with support for both local networks and public servers.27 npm1ISC
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to audit server health and operations through read-only tools, including container status, logs, alerts, and WhatsApp session status, without requiring SSH access.-
- FlicenseNot gradedqualityCmaintenanceEnables LLMs to monitor server health through natural language, including HTTP endpoint checks, disk/memory/CPU usage, port status, and process listings.-
- AlicenseBqualityAmaintenanceMCP server enabling local network interaction, shell command execution, system resource monitoring, and SSH-based remote device management.18MIT
- AlicenseAqualityBmaintenanceEnables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.128 npm1MIT
TDQS
Scored across 19 tools
Most tools have distinct purposes, with clear separation between monitoring (e.g., get_system_load, monitor_processes), Docker operations (e.g., list_docker_containers, check_docker_health), and security tasks (e.g., security_vulnerability_scan, check_ssh_risk_logins). However, some overlap exists between analyze_logs and get_container_logs, as both involve log analysis, which could cause minor confusion.
The naming follows a consistent verb_noun pattern in snake_case for most tools (e.g., check_service_status, get_memory_info), making them predictable and readable. The only deviation is _list_available_tools, which uses an underscore prefix and is less descriptive, but this is a minor inconsistency in an otherwise uniform set.
With 19 tools, the count is slightly high but reasonable for an operations server covering monitoring, Docker, and security. It avoids being overwhelming (e.g., not 25+ tools) and provides comprehensive coverage without excessive redundancy, though it could be streamlined by merging some overlapping functions.
The tool set offers good coverage for server operations, including monitoring (e.g., get_system_load), Docker management (e.g., list_docker_containers), and security (e.g., security_vulnerability_scan). Minor gaps exist, such as lack of tools for updating configurations or handling backups beyond critical files, but agents can work around these with existing tools.