Zabbix MCP Server
Related Servers
Alternatives to Zabbix MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceExposes 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.10023 PyPIMIT
- 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.84251AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceExposes Zabbix monitoring capabilities as callable tools for AI agents and MCP-compatible clients.-
- AlicenseBqualityBmaintenanceEnables 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 to a distinct resource and action, making core selection straightforward. The main ambiguous pairs are problem_get vs event_get and discoveryrule_get vs drule_get, where descriptions are needed to clarify the boundary.
The dominant pattern is predictable snake_case resource_action naming, such as host_get, host_create, and trigger_update. Minor deviations include api_version lacking an action verb, drule_get abbreviating discoveryrule_get, and compact compounds like hostgroup and usermacro.
With 53 tools, the server is far above the well-scoped 3-15 range and places a heavy burden on tool selection. The broad Zabbix domain justifies many operations, but the set still feels unwieldy and includes many separate read-only getters.
Core monitoring objects such as hosts, host groups, items, triggers, templates, maintenance, users, and proxies have CRUD coverage, and history/trends/events are readable. However services, SLAs, actions, media types, graphs, discovery rules, and scripts are largely read-only or missing create/update/delete, leaving notable lifecycle gaps.