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_program_status_toolA | Check whether the Nagios daemon itself is alive and actually working. Use this to verify the monitoring system, NOT to find outages. It is the right tool for a watchdog asking "is Nagios still able to tell me about problems?" -- nagios_current_problems_tool answers a different question and returns "no problems" both when all is well and when Nagios has silently stopped working. Detects a wedged daemon (CGI still returns 200 but status data is stale), globally disabled notifications (monitoring everything, alerting nobody), and disabled check execution. Raises on connection failure, so a dead Nagios can never be read as healthy. |
| 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 8 tools
Each tool targets a distinct Nagios resource or action: daemon health, current problems, host/service status, acknowledgements, comments, notification history, and scheduled checks. The program_status tool is explicitly differentiated from current_problems to avoid confusion.
All tools follow a consistent pattern: 'nagios_' prefix, snake_case middle describing the operation or resource, and '_tool' suffix. The naming is uniform and predictable.
8 tools is well-scoped for a Nagios monitoring server, covering status queries, problem actions, and operational checks without being overly granular or sparse.
The toolset covers core Nagios operations: status retrieval, problem listing, acknowledgements, comments, notification history, and forced checks. Missing operations like disabling notifications or deleting comments are minor gaps that don't severely hinder common workflows.