No user-submitted related servers found.
Scored across 84 tools
Most tools target distinct Zabbix object types, but there are several overlapping pairs: problem_get vs problem_active_get, history_get vs item_history_summary_get, host_get vs host_status_get, hostgroup_get vs hostgroup_overview_get, and item_get vs item_threshold_search. The descriptions explicitly steer the agent between raw and composite tools, which helps, but the large surface still creates meaningful selection ambiguity.
The dominant pattern is snake_case noun_verb (host_get, item_get, problem_get), matching Zabbix API conventions, but action-oriented tools use verb_noun (graph_render, anomaly_detect, capacity_forecast, report_generate) and a few names are irregular (apiinfo_version, health_check, user_checkauthentication, sla_getsli, script_getscriptsbyevents). The convention is readable but not uniform.
84 tools is very heavy for an MCP server, even one covering the broad Zabbix API. Many are near-duplicate read-only getters plus composite convenience wrappers, so the set feels over-expanded rather than tightly scoped.
The surface is overwhelmingly read-only: it covers retrieval for many object types but lacks create/update/delete operations for hosts, items, triggers, maintenance, users, and most other resources. It also lacks common operational actions such as acknowledging or closing problems, so an agent cannot complete many lifecycle workflows.