Zabbix MCP Server Universal
Related Servers
Alternatives to Zabbix MCP Server Universal
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceZabbix 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+.15Apache 2.0
- AlicenseBqualityAmaintenanceEnables 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
- 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
- AlicenseAqualityCmaintenance🔌 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.3261GPL 3.0
- 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.-
TDQS
Scored across 100 tools
Many tools overlap heavily: listar/consultar pairs exist for hosts, items, triggers, problems, templates and proxies, while 'gerenciar' tools (grupos_hosts, acoes, proxies, regras_descoberta, grupos_templates) partially duplicate the dedicated create/update/delete tools. Seven gerar_relatorio_* variants (executivo, disponibilidade, problemas, desempenho, inventario, capacidade, sla) plus consultar_sla_servico and gerar_relatorio_sla are hard to separate, and diagnosticar_coleta/verificar_coleta/detectar_lacunas_coleta/diagnosticar_ambiente form a fuzzy cluster. An agent can often guess, but misselection is likely.
All names follow the zabbix_ prefix plus snake_case Portuguese verb_noun convention, which is predictable and readable. Minor deviations exist (mixed verb families like listar vs consultar for reads, and bundling verbs like gerenciar/ativar_desativar that combine multiple actions into one name), but the pattern itself is stable throughout.
100 tools for a single Zabbix integration is an extreme surface that far exceeds what an agent can reliably navigate, and the rubric places 50+ tools at the bottom. Many entries are hyper-granular (checking gaps, comparing periods, explaining metrics) and could be collapsed into a handful of parameterized tools.
Coverage is broad: hosts, items, triggers, problems, events, services, maintenance, maps, inventory, templates, discovery rules/LLD, proxies, users, audit and system state, plus reporting and analytics. Gaps remain around write operations for some resources (no delete_item, delete_trigger, delete_service, delete_maintenance, delete_template), and user/dashboard/script management is read-only or absent, but agents can work around most of these.