zapi-mcp
Related Servers
Alternatives to zapi-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server to access the Zabbix API, providing tools to list hosts, problems, triggers, items, history, and events.-
- AlicenseCqualityFmaintenanceComprehensive MCP server for integrating with Zabbix monitoring systems, providing 90+ API tools across 19 categories for monitoring, alerting, and infrastructure management.10015MIT
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server that provides Zabbix monitoring data to AI agents, enabling investigation of hosts, metrics, incidents, and triggers with deterministic aggregation.-
- 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
- AlicenseAqualityBmaintenance🔌 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.3259GPL 3.0
- AlicenseBqualityDmaintenanceAn MCP server that provides operational tooling over the Zendesk Support API — ticket triage, SLA monitoring, agent workload analysis, and system health audits.111MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct role: daily_brief is an aggregated summary, get_problems is a raw problem query, get_hosts and get_host_items target different host data, health_check checks server status, acknowledge_problem and set_maintenance perform distinct actions, and get_maintenance_windows is the read-side counterpart. The descriptions explicitly clarify boundaries (e.g., acknowledge vs. suppress new notifications, daily_brief vs. get_problems). No two tools appear to do the same thing.
Most tools follow a verb_noun pattern (get_hosts, get_problems, acknowledge_problem, get_host_items, get_maintenance_windows, set_maintenance). Two tools (daily_brief, health_check) use noun phrases instead, which is a minor deviation but still readable and consistently snake_case throughout.
Eight tools is well-scoped for a Zabbix monitoring server, covering read operations, a curated summary, health checking, and two targeted write actions without excess. Each tool earns its place and the count avoids feeling either thin or bloated.
The surface covers core monitoring workflows: problem listing and acknowledgement, host and item queries, maintenance window creation and viewing, a daily brief, and a health check. Minor gaps exist—no update/delete for maintenance windows (they only expire), no item history or trend retrieval, and no direct problem-resolution action—but these are either non-standard in Zabbix or workable around.