Zabbix

Getting a token (Zabbix 5.4 and newer)

1. Sign in to the Zabbix frontend as a Super admin and open Users → API tokens.
2. 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.
3. Set ZABBIX_URL to your frontend root (no trailing slash, no /api_jsonrpc.php) and ZABBIX_API_TOKEN to the token. The adapter sends it as Authorization: Bearer …, which Zabbix 6.0+ accepts; on 5.4 the token also works in the JSON-RPC auth field, which this adapter does not use.

One endpoint, many methods. Zabbix is JSON-RPC: every call is a POST to /api_jsonrpc.php with {"jsonrpc":"2.0","method":"host.get","params":{…},"id":1}. That is why every tool here has the same path, and why the method is what distinguishes them.

Permissions are per host group, and Zabbix reports a denial as an empty array. A token whose user cannot see a host group gets {"result": []} rather than an error — so an agent that reports 'no problems' may simply be looking through an account with no visibility.

Severity is an integer. 0 not classified, 1 information, 2 warning, 3 average, 4 high, 5 disaster. 'Critical alerts' usually means severity ≥ 4.

problem.get is the live board, event.get is the history. A problem that has since resolved is gone from problem.get and still in event.get. Ask the right one.

Timestamps are Unix seconds, in the server's timezone configuration.

Self-hosted, which is the thing to plan for.

• On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch, and a homelab's default certificate is exactly the case that breaks.
• On an internal host (zabbix.intern, 10.0.0.x), self-host AnythingMCP on the same network and add that host to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.