Skip to main content
Glama

Related Servers

Alternatives to mcp-zabbix

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Official initMAX MCP server exposing the Zabbix API to AI assistants for monitoring and managing hosts, problems, templates, dashboards, and multiple Zabbix instances. Includes correlated monitoring views, graphs, anomaly detection, capacity forecasts, and PDF reports, with scoped tokens, read-only modes, OAuth 2.1, and an admin portal. Supports Streamable HTTP, SSE, and stdio.
      86
      241
      AGPL 3.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes Zabbix monitoring capabilities as callable tools for AI agents and MCP-compatible clients.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to monitor and query Zabbix infrastructure through natural language by providing access to current problems, active triggers, and system health status via the Zabbix API.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Zabbix MCP server and CLI in one Go binary. 15 task-shaped tools: current problems, host investigation, why an alert did or did not arrive, metrics, maintenance. Zabbix 6.4+.
      15
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      🔌 Complete MCP server for Zabbix integration - Connect AI assistants to Zabbix monitoring with 40+ tools for hosts, items, triggers, templates, problems, and more. Features read-only mode and comprehensive API coverage.
      3
      260
      GPL 3.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to query and manage Zabbix monitoring data—hosts, items, triggers, problems, and health checks—and generate daily, weekly, and monthly operations reports.
      21
      GPL 3.0

    TDQS

    C2/5.0

    Scored across 262 tools

    Disambiguation5/5

    Every tool name combines a resource with an operation (e.g., zabbix_host_get, zabbix_graph_delete), so each tool is clearly distinct. No two tools appear to overlap in purpose.

    Naming Consistency5/5

    All tools follow the identical zabbix_<entity>_<operation> pattern, making the set highly predictable and internally consistent.

    Tool Count1/5

    With 262 tools, the set is far too large for an MCP server. This would overwhelm context windows and make tool selection impractical. Even the most comprehensive APIs rarely need this many distinct tool entries.

    Completeness2/5

    Coverage is uneven: many core Zabbix entities (action, alert, hostgroup, proxy, script, etc.) are missing, while obscure entities like dcheck/dhost are over-represented. The presence of 'exists' methods for only some resources also suggests arbitrary generation rather than deliberate API coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues