Skip to main content
Glama
crunchtools

mcp-nagios-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-nagios-crunchtools

No user-submitted related servers found.

    Related Servers

    • nagios-mcp

      equilibrise
      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

    • vibeMK-MCP

      SirTificate
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language management of CheckMK monitoring environments, including host/service monitoring, downtime scheduling, problem acknowledgement, and configuration management through LLM interfaces.
      GPL 3.0

    • thruk-mcp

      k9fr4n
      A
      license
      C
      quality
      B
      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

    • nable-rmm-mcp

      MSPbotsAIFramework
      A
      license
      Not graded
      quality
      B
      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

    • Linuxfabrik MCP Server for

      Linuxfabrik
      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
      -

    • mcp-prtg

      dmayan-ss
      F
      license
      A
      quality
      D
      maintenance
      Enables querying sensors, devices, groups, channels, historical data, and system status from a PRTG Network Monitor instance via the classic PRTG HTTP API.
      9
      2
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct Nagios concept or action: current problems vs. daemon health (explicitly contrasted), host status vs. service status, notification history vs. alert history (differentiated by scope). The descriptions actively call out the tricky overlaps, leaving little room for misselection.

    Naming Consistency5/5

    Every tool follows the same nagios_<concept>_tool snake_case pattern with a uniform prefix and suffix. Action tools (acknowledge, add_comment, schedule_check) and query tools are all rendered in the identical convention.

    Tool Count5/5

    Nine tools is well-scoped for a Nagios monitoring/inspection surface, with each tool earning its place covering distinct read and light-action operations. No redundancy or filler.

    Completeness4/5

    Core monitoring workflows are covered: problem listing, daemon health, host/service status, acknowledgement, comments, forced checks, and two history views. Minor gaps exist around scheduled downtime and enable/disable notifications, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources