Zabbix MCP Server
Related Servers
Alternatives to Zabbix MCP Server
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseAqualityBmaintenanceZabbix 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
- 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.84247AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to query Zabbix monitoring data through MCP, including host briefs and problem reports, with read-only access and whitelist controls.-
- FlicenseNot gradedqualityCmaintenanceExposes Zabbix monitoring capabilities as callable tools for AI agents and MCP-compatible clients.-
- AlicenseAqualityDmaintenance🔌 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.3260GPL 3.0
TDQS
Scored across 21 tools
Several read-oriented tools overlap around current problems, host health, quick status, and event history: get_problem_summary, get_problem_fact_detail, check_host_health, quick_status, host_alert_history, and event_get can be confused despite their descriptions. The descriptions do provide guidance, but boundaries are not always crisp.
All names use snake_case, but verb/noun ordering is mixed: host_get, item_get, event_get, and trend_get use noun_verb, while get_problem_summary, get_host_by_ip, and check_host_health use verb_noun, and others like quick_status and apiinfo_version are noun phrases. The conventions are readable but inconsistent.
21 tools is on the heavy side, but Zabbix is a broad monitoring domain covering hosts, groups, items, triggers, events, history, trends, reports, and health checks. Most tools map to distinct data needs, though a few status/problem tools could be consolidated.
The read surface is strong: hosts, groups, software inventory, items, triggers, events, history, trends, health checks, and daily/weekly/monthly reports are covered. Write/lifecycle coverage is thinner, with host_update but no host create/delete, problem acknowledgement, maintenance, or template/user management, which are notable but not fatal for a query/report-focused server.