Zabbix MCP Server
Related Servers
Alternatives to Zabbix MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceExposes 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.100MIT
- AlicenseBqualityAmaintenanceOfficial 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.86245AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceExposes Zabbix monitoring capabilities as callable tools for AI agents and MCP-compatible clients.-
- AlicenseBqualityCmaintenanceEnables AI assistants to query and manage Zabbix monitoring data—hosts, items, triggers, problems, and health checks—and generate daily, weekly, and monthly operations reports.21GPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseNot gradedqualityCmaintenanceExposes the entire Zabbix API as MCP tools so AI assistants and other MCP clients can query hosts, inspect problems, manage templates and dashboards, acknowledge events, and perform other Zabbix operations. It also adds pre-correlated summary views, graph rendering, anomaly detection and forecasting, PDF report generation, and a two-step write approval flow, with multi-server, token-scoped and read-only deployment options.AGPL 3.0
TDQS
Scored across 53 tools
Most tools map clearly to a distinct Zabbix resource and action, with descriptions distinguishing similar resources such as items vs. item prototypes and LLD discovery rules vs. network discovery rules. A few pairs (event_get vs. problem_get, discoveryrule_get vs. drule_get) still require careful reading, preventing a perfect score.
The set overwhelmingly follows a predictable snake_case resource_action pattern (host_get, host_create, host_update, host_delete, item_get, etc.). Minor deviations exist, such as api_version and the abbreviated drule_get alongside discoveryrule_get, but overall naming is consistent.
At 53 tools, the surface is far above the typical well-scoped range and is heavy for an agent to navigate reliably. While Zabbix is a broad domain, many tools could be consolidated or scoped into separate server configurations.
Core host, host group, template, item, trigger, user, proxy, and maintenance lifecycles have full CRUD coverage, and many read operations are present. However, significant resources such as actions, media types, graphs, services, SLAs, item prototypes, and discovery rules are read-only or lack update/delete operations, leaving notable gaps.