Zabbix MCP — Claude Code MCP server for Zabbix monitoring
A Python MCP server that lets an AI agent read and change Zabbix data: hosts, triggers, problems, maintenance windows.
claude mcp add --env ZABBIX_URL=<ZABBIX_URL> --env ZABBIX_TOKEN=<ZABBIX_TOKEN> --env ZABBIX_USER=<ZABBIX_USER> --env ZABBIX_PASSWORD=<ZABBIX_PASSWORD> --env ZABBIX_VERIFY_SSL=<ZABBIX_VERIFY_SSL> --transport stdio zabbix-mcp -- uvx zabbix-mcpWhat Zabbix MCP does
Zabbix MCP wires an agent into the Zabbix API. It hands over hosts, templates, items, triggers and host groups with filtering, plus problems, events and alerts filtered by severity. History and trend data for monitored items come through the same way, along with user macros, SLA and service information. Writes are supported too: creating, updating and deleting hosts, templates and host groups, managing triggers, items and discovery rules, running scripts on monitored hosts, acknowledging events and closing problems.
Install it from PyPI with uvx zabbix-mcp or pip install zabbix-mcp. You need Python 3.11 to 3.15 and a reachable Zabbix server in the 6.0 to 7.4 range, since the zabbix-utils client refuses to connect outside it unless ZABBIX_SKIP_VERSION_CHECK=true is set. Set ZABBIX_URL and ZABBIX_TOKEN, or ZABBIX_USER with ZABBIX_PASSWORD, before starting the server.
READ_ONLY_MODE=true turns off every write operation, which is the setting to pick if the agent should only look. Tool exposure narrows through DISABLED_TAGS, and request volume is capped by RATE_LIMIT_ENABLED, RATE_LIMIT_MAX_REQUESTS and RATE_LIMIT_WINDOW_MINUTES. Three transports are available: STDIO, SSE and HTTP. The Docker image serves HTTP Streamable on port 8000 at /mcp, guarded by the MCP_HTTP_BEARER_TOKEN bearer token.
What it helps with
- see which hosts are currently in a problem state
- pull item history for a given time range
- schedule a maintenance window before work on a host
- acknowledge an event and close a problem from the chat
- find hosts by group and template without clicking through the web UI
Example prompts for the agent
- List every Zabbix problem with Disaster severity or higher
- Create a two-hour maintenance window for host
db-01 - Show me the history for the
CPU utilizationitem over the last day
How to install Zabbix MCP
Platform CLI
claude mcp add --env ZABBIX_URL=<ZABBIX_URL> --env ZABBIX_TOKEN=<ZABBIX_TOKEN> --env ZABBIX_USER=<ZABBIX_USER> --env ZABBIX_PASSWORD=<ZABBIX_PASSWORD> --env ZABBIX_VERIFY_SSL=<ZABBIX_VERIFY_SSL> --transport stdio zabbix-mcp -- uvx zabbix-mcpReplace <…> with your own values. 13 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from zabbix-mcp <command>
Platform CLI
codex mcp add zabbix-mcp --env ZABBIX_URL=<ZABBIX_URL> --env ZABBIX_TOKEN=<ZABBIX_TOKEN> --env ZABBIX_USER=<ZABBIX_USER> --env ZABBIX_PASSWORD=<ZABBIX_PASSWORD> --env ZABBIX_VERIFY_SSL=<ZABBIX_VERIFY_SSL> -- uvx zabbix-mcpReplace <…> with your own values. 13 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from zabbix-mcp <command>
Config file
{
"mcpServers": {
"zabbix-mcp": {
"command": "uvx",
"args": [
"zabbix-mcp"
],
"env": {
"ZABBIX_URL": "<ZABBIX_URL>",
"ZABBIX_TOKEN": "<ZABBIX_TOKEN>",
"ZABBIX_USER": "<ZABBIX_USER>",
"ZABBIX_PASSWORD": "<ZABBIX_PASSWORD>",
"ZABBIX_VERIFY_SSL": "<ZABBIX_VERIFY_SSL>"
}
}
}
}Replace <…> with your own values. 13 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from zabbix-mcp <command>
Config file
{
"servers": {
"zabbix-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"zabbix-mcp"
],
"env": {
"ZABBIX_URL": "<ZABBIX_URL>",
"ZABBIX_TOKEN": "<ZABBIX_TOKEN>",
"ZABBIX_USER": "<ZABBIX_USER>",
"ZABBIX_PASSWORD": "<ZABBIX_PASSWORD>",
"ZABBIX_VERIFY_SSL": "<ZABBIX_VERIFY_SSL>"
}
}
}
}Replace <…> with your own values. 13 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from zabbix-mcp <command>
Platform CLI
gemini mcp add -e ZABBIX_URL=<ZABBIX_URL> -e ZABBIX_TOKEN=<ZABBIX_TOKEN> -e ZABBIX_USER=<ZABBIX_USER> -e ZABBIX_PASSWORD=<ZABBIX_PASSWORD> -e ZABBIX_VERIFY_SSL=<ZABBIX_VERIFY_SSL> zabbix-mcp uvx zabbix-mcpReplace <…> with your own values. 13 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from zabbix-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Zabbix MCP
How do I install Zabbix MCP in Claude Code?
Run claude mcp add zabbix-mcp -e ZABBIX_URL=<ZABBIX_URL> -e ZABBIX_TOKEN=<ZABBIX_TOKEN> -e ZABBIX_PASSWORD=<ZABBIX_PASSWORD> -- uvx zabbix-mcp, replacing the placeholders with your own values.
What does Zabbix MCP do?
It exposes the Zabbix API to an agent: hosts, triggers, problems, events, item history and SLA data for reading, plus write operations such as creating hosts and maintenance periods.
Which Zabbix versions does the server support?
6.0 through 7.4, the range the zabbix-utils client accepts. Outside it the connection fails unless ZABBIX_SKIP_VERSION_CHECK=true is set.
