Zabbix MCP Server

Zabbix MCP Server

    developed and maintained by
    
    and community


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


 
 
 
 
 
 

Table of Contents

Overview: What is this? · Features Install: Quick Start · Installation · Upgrade · First-time admin access Configure: Reference · OAuth 2.1 · Public URL · TLS / HTTPS · Token Budget Use: Client Wizard · AI Clients · Prompts · Tools · Parameters · Time zones · PDF Reports Operate: Installer CLI · Update notifications · Compatibility · Development · Related Projects · License

What is this?

MCP (Model Context Protocol) is an open standard that lets AI assistants (ChatGPT, Claude, VS Code Copilot, JetBrains AI, Codex, and others) use external tools. This server exposes the entire Zabbix API as MCP tools — allowing any compatible AI assistant to query hosts, check problems, manage templates, acknowledge events, and perform any other Zabbix operation.

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

Features

• Complete API coverage - All 58 Zabbix API groups (223 tools): hosts, problems, triggers, templates, users, dashboards, and more
• Extension tools (14) - Pre-correlated views: host_status_get, hostgroup_overview_get, infrastructure_summary_get, item_history_summary_get, problem_active_get (fold 3-5 raw API calls into one round-trip). Plus graph_render (PNG export), anomaly_detect (z-score analysis), capacity_forecast (linear regression), item_threshold_search (filter items by lastvalue thresholds), report_generate (PDF reports), action_prepare/action_confirm (two-step write approval), health_check (server diagnostics) and zabbix_raw_api_call (admin escape hatch for un-wrapped methods).
• Admin web portal - Full web UI on port 9090 for managing tokens, users, servers, templates, settings, and audit log; dark/light mode; point-and-click Client MCP Wizard (beta) that generates copy-paste-ready config snippets for 14 AI clients (Claude, Codex, Cursor, Cline, VS Code, JetBrains, Goose, Open WebUI, 5ire, Gemini CLI, n8n, ...)
• 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
• LLM-friendly normalizations - Symbolic enum names, auto-fill defaults, preprocessing cleanup, timestamp conversion with local-time rendering (<field>_local siblings and a per-call zone note, see Time zones)
• Single config file - One TOML file, no scattered environment variables
• Read-only mode - Per-server and per-token write protect