Zabbix MCP server

What the model can do

Zabbix monitoring, self-hosted or Zabbix Cloud: current problems, event history, hosts, items and their recent values. Can comment on, acknowledge, unacknowledge, re-grade, suppress, unsuppress, close and rank problems, create, change and delete maintenance windows, create and delete hosts, and enable or disable hosts, triggers and items.

Reads

• zabbix_list_host_groupsZabbix host groups (the group ids maintenances and new hosts take): group id and name.
• zabbix_list_maintenancesZabbix maintenance windows: id, name, when active, whether data is still collected, the hosts and host groups in it, and how many time periods.
• zabbix_list_triggersZabbix triggers on given hosts (the trigger ids zabbix_set_trigger_status takes): trigger id, description, severity, enabled…
• zabbix_list_templatesZabbix templates (the template ids zabbix_create_host can link): template id, technical and visible name.
• zabbix_list_problemsCurrent Zabbix problems (unresolved, plus recently resolved if asked), newest first: event id, name, severity, hosts, when it began…
• zabbix_list_eventsZabbix trigger events over a time window (default the last 24 hours), including resolved ones: event id, name, problem or recovery, severity, hosts…
• zabbix_list_hostsZabbix hosts: host id, technical and visible name, whether monitored, whether in maintenance, host groups and description.
• zabbix_list_itemsWhat Zabbix measures on given hosts: item id, name, key, last value and when, units.
• zabbix_item_historyAn item's recorded values over a window (default the last 24 hours), newest first, with min, max and average for numeric items.

Acts, when you ask

These change something in Zabbix. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• zabbix_create_maintenanceSILENCES ALERTS.
• zabbix_update_maintenanceSILENCES ALERTS.
• zabbix_delete_maintenanceDESTRUCTIVE.
• zabbix_set_host_statusSILENCES ALERTS when disabling.
• zabbix_create_hostAdds a host to Zabbix monitoring: a technical name, at least one host group id, and optionally a visible name, one Zabbix agent interface…
• zabbix_delete_hostDESTRUCTIVE.
• zabbix_set_trigger_statusSILENCES ALERTS when disabling.
• zabbix_set_item_statusSILENCES ALERTS when disabling.
• zabbix_comment_on_problemAdds a message to a Zabbix problem's history, as the token's user, without acknowledging, closing or changing it.
• zabbix_acknowledge_problemAcknowledges a Zabbix problem (marks it as being dealt with), optionally with a message.
• zabbix_unacknowledge_problemRemoves the acknowledgement from a Zabbix problem, optionally with a message saying why.
• zabbix_change_problem_severityChanges a Zabbix problem's severity, REPLACING the current one (the old severity stays in the problem's history and can be set back with this tool)…
• zabbix_suppress_problemSuppresses a Zabbix problem, hiding it from problem views and stopping escalation, until the given time or indefinitely.
• zabbix_unsuppress_problemEnds the suppression of a Zabbix problem so it shows and escalates again.
• zabbix_close_problemDESTRUCTIVE, closes a Zabbix problem by hand, marking it resolved although the trigger has not recovered.
• zabbix_mark_problem_as_causeRanks a Zabbix problem as a cause (undoing an earlier symptom ranking), which changes how its related problems are grouped.
• zabbix_mark_problem_as_symptomRanks a Zabbix problem as a symptom of another (the cause), which groups it under that problem in problem views.

Connect it

First connect Zabbix on Dashboard → Connections, then add Memtro to your client once. The Zabbix tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Zabbix connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which high-severity problems are unacknowledged right now?
• › What alerted on db-prod-02 overnight?
• › What was the CPU load on web-01 over the last 24 hours?
• › Which hosts are in maintenance at the moment?
• › Put db-prod-02 into maintenance from 22:00 to midnight tonight

Questions

Is this an official Zabbix MCP server?

No. It is Memtro's MCP server with Memtro's Zabbix connector behind it: the connector reads Zabbix through its API with the credentials you connect on Dashboard → Connections, and Zabbix publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Zabbix?

Only when you ask, and only what it has been granted: add a comment to a problem; acknowledge a problem; unacknowledge a problem; change a problem's severity; suppress a problem, until a time or indefinitely; unsuppress a problem; close a problem by hand; mark a problem as the cause of others; mark a problem as a symptom of another; put hosts or host groups into a maintenance window (suppresses their alerts); change a maintenance window's times, hosts or groups; delete a maintenance window (permanent); turn monitoring of a host on or off; add a host to monitoring; delete a host and its history (permanent); enable or disable a trigger; enable or disable an item. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server