mcp-nagios-crunchtools
# mcp-nagios-crunchtools
Secure MCP server for Nagios Core monitoring. Query host and service status, acknowledge problems, add comments, schedule forced checks, and read notification history.
## Installation
```bash
uvx mcp-nagios-crunchtools
```
## Configuration
| Variable | Required | Description |
|----------|----------|-------------|
| `NAGIOS_URL` | Yes | Base URL (e.g., `https://nagios.crunchtools.com`) |
| `NAGIOS_USER` | Yes | HTTP Basic Auth username |
| `NAGIOS_PASS` | Yes | HTTP Basic Auth password |
## Tools
| Tool | Description |
|------|-------------|
| `nagios_host_status` | Query a single host's status |
| `nagios_service_status` | Query a single service's status |
| `nagios_current_problems` | All hosts/services not in OK state |
| `nagios_acknowledge` | Acknowledge a host or service problem |
| `nagios_add_comment` | Add a comment to a host or service |
| `nagios_schedule_check` | Force an immediate re-check |
| `nagios_notification_history` | Recent notifications |
## License
AGPL-3.0-or-later
TDQS
Scored across 7 tools
Each tool targets a distinct facet of Nagios operations: host status, service status, problem aggregation, acknowledgments, comments, forced checks, and notification history. There is no meaningful overlap between these actions.
All tools share the nagios_ prefix and snake_case naming, and most follow a clear action-oriented pattern like acknowledge, add_comment, schedule_check. Even the status tools are clearly recognizable as noun-based descriptors.
With 7 tools, the server is well-scoped for common Nagios workflows: status inspection, problem triage, acknowledgment, comments, active checks, and history. It avoids both bloat and unnecessary sparseness.
The toolset covers the primary monitoring lifecycle well, including view statuses, list problems, acknowledge, comment, re-check, and review history. Downtime scheduling and custom commands are notable omissions but not critical for daily monitoring operations.