Skip to main content
Glama
k9fr4n

thruk-mcp

by k9fr4n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to thruk-mcp

No user-submitted related servers found.

    Related Servers

    • vibeMK-MCP

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

    • mcp-centreon

      fredriksknese
      F
      license
      A
      quality
      C
      maintenance
      MCP server for Centreon IT monitoring that enables querying host/service status, managing acknowledgements and downtimes, and retrieving performance metrics via natural language.
      17
      -

    • vibeMK

      chexma
      A
      license
      C
      quality
      D
      maintenance
      Enables complete management of CheckMK monitoring environments through natural language, including live monitoring, downtime scheduling, problem management, and configuration.
      115
      17
      GPL 3.0

    • mcp-uptime-kuma

      DavidFuchs
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Uptime Kuma that enables monitoring and management of uptime monitors, heartbeats, notifications, tags, and maintenance windows via natural language.
      31
      274 npm
      51
      MIT

    • helpdesk-workflow

      cust0diodev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language queries to Tactical RMM, GLPI/TurboDesk, Zabbix, and Grafana for IT alerts, agents, tickets, problems, and dashboard metadata through a local MCP stdio server.
      1
      MIT
    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

    C2.9/5.0

    Scored across 65 tools

    Disambiguation4/5

    Most tools have distinct purposes, but similarities among problem- and alert-related tools (e.g., thruk_problems, thruk_oldest_problems, thruk_problem_counts, thruk_recurring_problems) may cause confusion if descriptions are not carefully read.

    Naming Consistency4/5

    All tools start with 'thruk_' and follow a mostly verb_noun pattern (e.g., list_hosts, schedule_downtime). Some are just nouns (stats, totals), but deviations are minor.

    Tool Count2/5

    With 65 tools, the set is excessively large for an agent to navigate efficiently. Many tools could be merged or parameterized to reduce cognitive load.

    Completeness4/5

    The tool set covers the main monitoring lifecycle (list, get, acknowledge, comment, downtime, availability, perfdata). The thruk_query escape hatch fills gaps, though some update/configuration operations are missing.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources