Integration

Zabbix integration

Zabbix monitoring API for a self-hosted server: read and manage hosts, host groups, items and triggers, list the problems that are currently open, read event history and acknowledge or close events, pull collected metric values from history and trends, and inspect templates and maintenance windows. The whole API is JSON-RPC over a single endpoint, so each tool here pins one API method. Point the credential at your own Zabbix frontend and authenticate with an API token created under Users, API tokens.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Zabbix.Built from the 15 Zabbix tools below, on the connection you add once.

Common Zabbix use cases

  • removing monitoring for a decommissioned server
  • registering a newly provisioned server for monitoring
  • charting a month of average load for a capacity review
  • stopping monitoring on a host while it is being rebuilt
  • resolving a host group identifier before creating a host
  • listing which triggers are currently in the problem state
  • pulling the last hour of CPU samples for a host into a report
  • adding a custom metric to a host that a template does not cover
  • resolving a template identifier before linking it to a new host
  • building an on call feed of the problems that are currently open

What you can do with Zabbix

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Host, 4 operations

  • create_hostCreate hostPOSTCreates a Zabbix host in one or more host groups.
  • delete_hostsDelete hostsPOSTDeletes Zabbix hosts and everything collected for them.
  • get_hostsGet hostsPOSTReads Zabbix hosts with their status and description.
  • update_hostUpdate hostPOSTUpdates the name, status or description of a Zabbix host.

Event, 2 operations

  • acknowledge_eventAcknowledge eventPOSTAcknowledges Zabbix events and can close them or change their severity.
  • get_eventsGet eventsPOSTReads Zabbix events including ones that are already resolved.

Item, 2 operations

  • create_itemCreate itemPOSTCreates a Zabbix item that collects one metric from a host.
  • get_itemsGet itemsPOSTReads Zabbix items, the individual metrics collected from a host.

History, 1 operation

  • get_historyGet historyPOSTReads collected Zabbix metric values for one or more items.

Host group, 1 operation

  • get_host_groupsGet host groupsPOSTReads Zabbix host groups.

Maintenance, 1 operation

  • get_maintenance_windowsGet maintenance windowsPOSTReads Zabbix maintenance windows and the period they cover.

Problem, 1 operation

  • get_problemsGet problemsPOSTReads the Zabbix problems that are currently open.

Template, 1 operation

  • get_templatesGet templatesPOSTReads Zabbix templates that can be linked to hosts.

Trend, 1 operation

  • get_trendsGet trendsPOSTReads hourly minimum, average and maximum Zabbix values from the trends tables.

Trigger, 1 operation

  • get_triggersGet triggersPOSTReads Zabbix triggers with their severity and current state.

Use Zabbix from Claude Code, Cursor or Codex

Connect Zabbix in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Zabbix operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Zabbix

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Zabbix once

    Add your Zabbix connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Zabbix integration FAQ

What can you do with the Zabbix integration?

LiveContext exposes 15 operations on Zabbix, covering host, event, item and history. Common uses include removing monitoring for a decommissioned server, registering a newly provisioned server for monitoring and charting a month of average load for a capacity review.

Popular integrations

Browse the whole catalog