mcp-zabbix
Related Servers
Alternatives to mcp-zabbix
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes the complete Zabbix API to MCP-compatible AI assistants, enabling natural language management of hosts, problems, and templates across multiple instances. It provides 220 tools for comprehensive monitoring and configuration with support for read-only modes and secure authentication.190AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceExposes Zabbix monitoring capabilities as callable tools for AI agents and MCP-compatible clients.-
- 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 gradedqualityAmaintenanceEnables AI agents to query Zabbix for current problems, host investigations, alert triage, metrics, and maintenance operations through task-shaped tools with bounded JSON output and human-approval safeguards for any changes.Apache 2.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.3251GPL 3.0
- AlicenseBqualityAmaintenanceProvides advanced, programmable access to Zabbix monitoring data and management features, enabling querying, automation, and integration of Zabbix resources.5310MIT
TDQS
Scored across 262 tools
Every tool name combines a resource with an operation (e.g., zabbix_host_get, zabbix_graph_delete), so each tool is clearly distinct. No two tools appear to overlap in purpose.
All tools follow the identical zabbix_<entity>_<operation> pattern, making the set highly predictable and internally consistent.
With 262 tools, the set is far too large for an MCP server. This would overwhelm context windows and make tool selection impractical. Even the most comprehensive APIs rarely need this many distinct tool entries.
Coverage is uneven: many core Zabbix entities (action, alert, hostgroup, proxy, script, etc.) are missing, while obscure entities like dcheck/dhost are over-represented. The presence of 'exists' methods for only some resources also suggests arbitrary generation rather than deliberate API coverage.