Zabbix MCP Server

Full Zabbix API access from Claude, Codex, VS Code, JetBrains, and other MCP clients.

The short version

The server runs as a standalone HTTP service. AI clients connect to it over the network.

• Complete API coverage — - All 58 Zabbix API groups (223 tools): hosts, problems, triggers, templates, users, dashboards, and more
• Multi-token authentication — - Named tokens with scopes, IP restrictions, server binding, expiry; managed via admin portal, CLI (generate-token), or config.toml
• Multi-server support — - Connect to multiple Zabbix instances (production, staging, ...) with separate tokens
• HTTP + SSE transports — - Streamable HTTP (recommended) and SSE for clients like n8n that lack session management
• Tool filtering — - Limit exposed tools by category (monitoring, alerts, users, extensions, etc.) or individual API prefix to reduce the tool catalog size and stay under LLM context limits (see Token Budget below)
• Compact output mode — - Get methods return only key fields by default, reducing response token usage; LLM can request extend for full details

What it needs from you

• Linux server with Python 3.10+ - Network access to your Zabbix server(s) - Zabbix API token (User settings > API tokens)

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.