Skip to main content
Glama
TemplarFan

Zabbix MCP Server

by TemplarFan

Related Servers

Alternatives to Zabbix MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query Zabbix for current problems, host investigations, alert triage, metrics, and maintenance operations through task-shaped tools with bounded JSON output and human-approval safeguards for any changes.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes the complete Zabbix API to MCP-compatible AI assistants, enabling natural language management of hosts, problems, and templates across multiple instances. It provides 220 tools for comprehensive monitoring and configuration with support for read-only modes and secure authentication.
      199
      AGPL 3.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query Zabbix monitoring data through MCP, including host briefs and problem reports, with read-only access and whitelist controls.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes Zabbix monitoring capabilities as callable tools for AI agents and MCP-compatible clients.
      -
    • 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
      253
      GPL 3.0

    TDQS

    B3.3/5.0

    Scored across 21 tools

    Disambiguation4/5

    大部分工具职责明确,如host_get与get_host_by_ip有明确的使用指引,history_get与trend_get也通过描述区分了数据粒度。但quick_status、check_host_health和get_problem_summary在“当前问题分类”上有重叠,可能造成选型困惑,整体上仍可通过描述消歧。

    Naming Consistency2/5

    命名风格明显不一致:一部分使用名词+动词(host_get, item_get, trigger_get),另一部分使用动词开头(get_host_by_ip, check_host_health, quick_status),还混合了报告类(event_daily_report等)和非标准命名(apiinfo_version)。缺乏统一的动词-名词模式,代理难以预测工具名称。

    Tool Count4/5

    21个工具对于Zabbix监控系统而言数量合理,覆盖了主机、组、监控项、触发器、事件、历史、趋势以及日报/周报/月报等核心查询场景。虽然略高于典型范围,但每个工具都有明确用途,并未出现冗余或空洞的工具。

    Completeness4/5

    查询面较为完整,包括主机、组、项、触发器、事件、历史、趋势和报告生成,且提供了问题摘要和健康检查等便捷功能。但缺少创建/删除主机、修改监控项或触发器之类的写操作,可能属于只读设计,整体上对于查询和报告覆盖良好。

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues