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

    • 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
      MIT

    • nable-rmm-mcp

      MSPbotsAI
      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.
      4
      -

    • 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
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessUnresponsive

    Resources