MCP server for Zabbix API - exposes all Zabbix API functionality via MCP
uvx mcp-zabbixAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-daedalus-mcp-zabbix": {
"command": "uvx",
"args": [
"mcp-zabbix"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
mcp-zabbix is an MCP server for MCP server for Zabbix API - exposes all Zabbix API functionality via MCP. It supports STDIO transport.
Use the generated config in Install. This server runs with uvx mcp-zabbix; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for uvx mcp-zabbix. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for uvx mcp-zabbix. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for uvx mcp-zabbix. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for uvx mcp-zabbix. Add required environment variables before starting Cursor or VS Code.
mcp-zabbix uses STDIO transport. Use the package or command config in Install.
mcp-zabbix inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
mcp-zabbix does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
mcp-zabbixstdio | pypi | 0.1.0 | None advertised |