mcp-nagios-crunchtools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAGIOS_URL | Yes | Base URL (e.g., https://nagios.crunchtools.com) | |
| NAGIOS_PASS | Yes | HTTP Basic Auth password | |
| NAGIOS_USER | Yes | HTTP Basic Auth username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nagios_host_status_toolA | Get the current status of a Nagios host. |
| nagios_service_status_toolC | Get the current status of a specific service on a host. |
| nagios_current_problems_toolA | List all hosts and services currently in a non-OK state. Returns: Summary of all current problems, or confirmation that everything is OK. |
| nagios_acknowledge_toolC | Acknowledge a host or service problem in Nagios. |
| nagios_add_comment_toolA | Add a persistent comment to a host or service in Nagios. |
| nagios_schedule_check_toolA | Schedule a forced immediate re-check of a host or service. |
| nagios_notification_history_toolA | Retrieve recent notification history from Nagios. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.