Mcp Zabbix
Query and manage Zabbix monitoring from your agent when triaging production alerts or auditing host and trigger coverage.
Overview
io.github.daedalus/mcp-zabbix is a MCP server for the Operate phase that exposes the full Zabbix API to AI agents over stdio.
What is this MCP server?
- Full Zabbix API surface exposed through MCP tools
- PyPI mcp-zabbix v0.1.0 with stdio MCP transport
- Supports agent-driven incident triage and config inspection
- GitHub source at daedalus/mcp-zabbix for self-hosted setups
- Version 0.1.0
- Claims full Zabbix API coverage via MCP
- PyPI identifier mcp-zabbix
What problem does it solve?
Operators lose time copying Zabbix context into chat when they want an agent to diagnose alerts or verify monitoring config.
Who is it for?
Indie operators running self-hosted or team Zabbix who want Claude or Cursor to query triggers, hosts, and API objects directly.
Skip if: Builders without a Zabbix instance or those who only need lightweight uptime pings.
What do I get? / Deliverables
After registration, your agent can call Zabbix API operations through MCP while you fix or iterate on production issues.
- MCP tools mapped to Zabbix API operations
- Agent-assisted alert and host investigations
- Documented monitoring checks without leaving the IDE
Recommended MCP Servers
Journey fit
How it compares
Zabbix API MCP integration, not a generic log grep skill or hosted APM SaaS.
Common Questions / FAQ
Who is io.github.daedalus/mcp-zabbix for?
Solo builders and small teams operating Zabbix who want MCP-aware agents to inspect and act on monitoring data.
When should I use io.github.daedalus/mcp-zabbix?
Use it in Operate/monitoring when triaging alerts, auditing coverage, or scripting API checks from your coding agent.
How do I add io.github.daedalus/mcp-zabbix to my agent?
Install mcp-zabbix from PyPI, configure stdio MCP, and supply Zabbix API URL and credentials per the repository README.