Skip to main content
Glama
mcp-nagios-crunchtools

mcp-nagios-crunchtools

by crunchtools

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NAGIOS_URLYesBase URL (e.g., https://nagios.crunchtools.com)
NAGIOS_PASSYesHTTP Basic Auth password
NAGIOS_USERYesHTTP 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.

MCP server for Nagios Core monitoring. Query host and service status, acknowledge problems, add comments, schedule forced checks, and read notification and alert history. Before planned work that will make checks fail (a deploy, a restart, a long work session), schedule downtime with nagios_schedule_downtime_tool and cancel it when done, so the work neither pages nor counts as noise. Notifications only fire on what Nagios is configured to page for; nagios_alert_history_tool shows every state change, including warnings and problems that recovered by themselves. To check whether Nagios ITSELF is alive and functioning -- as opposed to what it is reporting about other hosts -- use nagios_program_status_tool, not nagios_current_problems_tool.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
nagios_host_status_toolB

Get the current status of a Nagios host.

nagios_service_status_toolB

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.

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_toolB

Add a persistent comment to a host or service in Nagios.

nagios_schedule_check_toolC

Schedule a forced immediate re-check of a host or service.

nagios_schedule_downtime_toolA

Schedule fixed downtime starting now, before planned work makes checks fail.

Notifications stop for the window, and alert history counts problems inside it as planned work rather than noise. Cancel it with nagios_cancel_downtime_tool when the work is done.

nagios_list_downtimes_toolA

List scheduled downtime that is in effect or still to come.

nagios_cancel_downtime_toolA

End downtime this server scheduled, once the planned work is done.

Only downtime recorded under this server's own author is cancelled.

nagios_downtime_history_toolB

List past and current downtime windows, read from nagios.log.

nagios_notification_history_toolB

Retrieve recent notification history from Nagios.

nagios_alert_history_toolA

Roll up Nagios state changes per host and service over a period.

Unlike notification history, this includes warnings, soft states and problems that recovered without paging anyone, so it is where flapping shows.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 13 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityActive
ResponsivenessNo recent community issues