Skip to main content
Glama
mcp-nagios-crunchtools

mcp-nagios-crunchtools

by 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

uvx mcp-nagios-crunchtools

Related MCP server: thruk-mcp

Configuration

Variable

Required

Description

NAGIOS_URL

Yes

Base URL (e.g., https://nagios.example.com)

NAGIOS_USER

Yes

HTTP Basic Auth username

NAGIOS_PASS

Yes

HTTP Basic Auth password

NAGIOS_COMMENT_AUTHOR

No

Author recorded on acknowledgements and comments. Defaults to NAGIOS_USER. Not a tool parameter.

NAGIOS_CGI_PREFIX

No

Path under NAGIOS_URL where the CGI scripts are served. Defaults to /nagios/cgi-bin. Set to /cgi-bin for a Nagios served at the web root. A trailing slash is ignored.

NAGIOS_LOG_PATH

No

Read-only path to nagios.log. Enables nagios_downtime_history and the planned-work split in nagios_alert_history; archivejson.cgi never returns downtime entries.

TZ

Effectively yes

The container's local timezone. Must match the Nagios server's own timezone.

Why TZ matters

schedule_check submits a start_time to cmd.cgi, which parses it as naive wall-clock time in the Nagios server's local timezone — there is no offset field to send. The value is therefore built with time.localtime(), so this container must run in the same timezone as the Nagios server.

When it does not, forced checks are silently scheduled into the future by the offset between the two — four hours against an EDT server — and "check now" appears to do nothing at all. No error is raised. This was a real defect, fixed in 0.1.2 by switching from gmtime() to localtime(); the timezone assumption it introduced is why TZ belongs in this table rather than being left implicit.

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, with duration, attempt, acknowledgement and plugin output

nagios_program_status

Health check on the monitoring path itself (wedged daemon, disabled notifications, stale status) -- not the same as no current problems

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_schedule_downtime

Fixed downtime from now (5–480 min) on a host and its services, or one service, before planned work

nagios_list_downtimes

Downtime in effect or pending

nagios_cancel_downtime

End this server's own downtime when the work is done

nagios_downtime_history

Past and current downtime windows with author and comment, from nagios.log

nagios_notification_history

Recent notifications

nagios_alert_history

State changes rolled up per host/service, including warnings and problems that recovered by themselves; problems during scheduled downtime are totalled separately

License

AGPL-3.0-or-later

Available Tools

13 tools
nagios_acknowledge_toolNagios Acknowledge ToolC

Acknowledge a host or service problem in Nagios.

Inputs: comment (required), host_name (required), notify, sticky, +1 more. Returns: result

nagios_add_comment_toolNagios Add Comment ToolB

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

Inputs: comment (required), host_name (required), service_description. Returns: result

nagios_alert_history_toolNagios Alert History ToolA
Read-only

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.

Inputs: hours, host_name. Returns: result

nagios_cancel_downtime_toolNagios 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.

Inputs: host_name (required), service_description. Returns: result

nagios_current_problems_toolNagios Current Problems ToolA
Read-only

List all hosts and services currently in a non-OK state.

Inputs: no named parameters. Returns: result

nagios_downtime_history_toolNagios Downtime History ToolB
Read-only

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

Inputs: hours, host_name. Returns: result

nagios_host_status_toolNagios Host Status ToolB
Read-only

Get the current status of a Nagios host.

Inputs: host_name (required). Returns: result

nagios_list_downtimes_toolNagios List Downtimes ToolA
Read-only

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

Inputs: host_name. Returns: result

nagios_notification_history_toolNagios Notification History ToolB
Read-only

Retrieve recent notification history from Nagios.

Inputs: hours, host_name. Returns: result

nagios_program_status_toolNagios Program Status ToolA
Read-only

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.

Inputs: max_staleness_seconds. Returns: result

nagios_schedule_check_toolNagios Schedule Check ToolC

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

Inputs: host_name (required), service_description. Returns: result

nagios_schedule_downtime_toolNagios 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.

Inputs: comment (required), minutes (required), host_name (required), service_description. Returns: result

nagios_service_status_toolNagios Service Status ToolB
Read-only

Get the current status of a specific service on a host.

Inputs: host_name (required), service_description (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
      -
    • A
      license
      C
      quality
      C
      maintenance
      Enables natural language interaction with Thruk monitoring systems, allowing users to query hosts/services, schedule downtimes, acknowledge problems, and more via MCP-compatible clients.
      65
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Nagios Core that enables querying host and service status, alerts, configuration, and other monitoring data through CGI binaries.
      5
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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