Skip to main content
Glama
mhajder

Zabbix MCP Server

by mhajder

Related Servers

Alternatives to Zabbix MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      C
      maintenance
      Exposes the complete Zabbix API functionality through the Model Context Protocol, mapping API methods to tools for managing hosts, triggers, and monitoring data. It enables seamless integration and control of Zabbix monitoring environments via natural language interfaces.
      100
      MIT
    • 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.
      190
      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
      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
      C
      quality
      F
      maintenance
      Comprehensive MCP server for integrating with Zabbix monitoring systems, providing 90+ API tools across 19 categories for monitoring, alerting, and infrastructure management.
      100
      15
      MIT

    TDQS

    B3.3/5.0

    Scored across 53 tools

    Disambiguation4/5

    Most tools follow a clear entity+action pattern with each resource and operation distinctly named. However, discoveryrule_get and drule_get both involve 'discovery' concepts and could be confused by an agent, and item_get/history_get/trend_get require careful reading to separate.

    Naming Consistency4/5

    The vast majority of tools use a consistent snake_case noun_verb pattern (e.g., host_get, host_create, host_update, host_delete). Minor deviations exist with api_version (noun_noun) and event_acknowledge (non-CRUD verb), but these do not seriously undermine predictability.

    Tool Count1/5

    With 53 tools, this server vastly exceeds the typical coherent MCP tool count and falls into the extreme range. Even though Zabbix is a broad domain, this tool list would overwhelm agents and could be consolidated.

    Completeness3/5

    Core entities like hosts, items, triggers, users, proxies, and maintenance periods have full CRUD coverage. However, many non-core areas such as actions, media types, graphs, discovery rules, services, and SLAs are read-only, and usermacros lack an update operation, leaving noticeable gaps for full lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive