Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Zabbix in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Zabbix monitoring: hosts, host groups, items, triggers, active problems, events and the latest measured values. JSON-RPC API over a single endpoint, bearer API token.
Try asking
Example prompts for Zabbix
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Zabbix, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Zabbix
Zabbix monitoring: hosts, host groups, items, triggers, active problems, events and the latest measured values. JSON-RPC API over a single endpoint, bearer API token.
Setup
Getting a token (requires Zabbix 6.4 or newer)
- Sign in to the Zabbix frontend as a Super admin and open Users → API tokens.
- Create a token for a user with read permission on the host groups the agent should see, and copy the value — Zabbix shows it once.
- Set
ZABBIX_URLto your frontend root (no trailing slash, no/api_jsonrpc.php) andZABBIX_API_TOKENto the token. The adapter sends it asAuthorization: Bearer …, which Zabbix accepts from 6.4 on. Zabbix 5.4–6.2 only take the token in the JSON-RPCauthfield, which this adapter does not use, so every call there fails with "Not authorised".
…(continued in the in-app connector instructions)
Prerequisites: ZABBIX_URL, ZABBIX_API_TOKEN
Install the connector locally
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Open http://localhost:3000/connectors/store, pick Zabbix and paste in the env vars listed under Prerequisites.
Available tools
| Tool | What it does |
|---|---|
zabbix_get_api_version | Read the Zabbix API version |
zabbix_list_hosts | List monitored hosts with their name, status, interfaces and host groups |
zabbix_list_host_groups | List host groups with their id, name and the number of hosts in each |
zabbix_list_problems | List the problems that are active right now, with their severity, host, name and the time they started |
zabbix_list_events | List events from the history — including problems that have since resolved, which problem |
zabbix_list_triggers | List triggers with their expression, severity, current value and the host they belong to — the rules that turn measurements into problems |
zabbix_list_items | List monitored items with their key, name, type, value type and units — what Zabbix actually measures on a host |
zabbix_get_latest_values | Read the most recent value of specific items — the current disk usage, load average or temperature, rather than the alert about it |
zabbix_get_history | Read historical values of one item over a time range — the series behind a graph |
zabbix_list_maintenance_windows | List configured maintenance windows with their hosts, groups and periods — the explanation for why an alert did not fire |
Next steps
Was this guide helpful?
