mcp-nagios-crunchtools
Related Servers
Alternatives to mcp-nagios-crunchtools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Nagios Core that enables querying host and service status, alerts, configuration, and other monitoring data through CGI binaries.5Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables natural-language monitoring and management of a Centreon instance, including real-time status checks, configuration operations, incident response, metrics analysis, and guided host diagnosis, with pluggable authentication and role-based tool access.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables natural language management of CheckMK monitoring environments, including host/service monitoring, downtime scheduling, problem acknowledgement, and configuration management through LLM interfaces.GPL 3.0
- AlicenseCqualityCmaintenanceEnables natural language interaction with Thruk monitoring systems, allowing users to query hosts/services, schedule downtimes, acknowledge problems, and more via MCP-compatible clients.652MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with N-able RMM (N-sight) API to manage clients, sites, devices, and retrieve monitoring data such as checks, patches, and performance history.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI clients like Claude to triage, investigate, and operate Icinga installations through natural language, integrating with Icinga's REST APIs and providing deep awareness of monitoring plugins and historical performance data.5-
TDQS
Scored across 13 tools
Each tool targets a distinct action or data view, and descriptions actively disambiguate tricky pairs (program_status vs current_problems, alert_history vs notification_history, downtime_history vs list_downtimes). The only mild overlap is between downtime_history ('past and current') and list_downtimes ('in effect or still to come'), which could still confuse an agent about which covers active windows.
All 13 tools follow the same nagios_<verb/noun>_tool pattern (nagios_acknowledge_tool, nagios_schedule_downtime_tool, etc.), with no camelCase or style mixing. Predictable and easy to scan.
13 tools is well within the ideal range and each maps to a concrete monitoring operation (status queries, acknowledgements, comments, downtime lifecycle, history, self-health). No filler or redundant tools are apparent.
Core read lifecycle (host/service status, current problems, program status) and downtime lifecycle (schedule/cancel/list/history) plus acknowledgement and comments are covered. Minor gaps exist: no unacknowledge/remove-comment, no enable/disable notifications, and no host/service inventory enumeration, but these are workaroundable.