Zabbix-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| READ_ONLY | No | READ_ONLY (default on) hard-blocks every mutating method. | true |
| ZABBIX_URL | Yes | The URL of the Zabbix server. | |
| MCP_TRANSPORT | No | Transport mode; set to stdio to keep stdout clean for the protocol. | |
| CONFIRM_WRITES | No | Controls two-step writes; one of all, destructive, or none. | |
| ZABBIX_API_TOKEN | Yes | Zabbix API token used to authenticate with the Zabbix server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_active_problemsC | Current unresolved problems (newest first) with host, severity and age. |
| get_host_detailsB | Status, interfaces, groups, templates, tags and item/problem counts for one host. |
| search_hostsB | Find hosts by name, technical name, IP or DNS. |
| list_host_groupsC | Host groups with host counts. |
| get_triggersC | Triggers (monitored, enabled) with severity and state. |
| get_latest_valuesC | Latest collected values of a host's items, optionally filtered by name/key. |
| query_metrics_historyA | History (or trends for windows >48h) of up to 5 matching items, downsampled to min/avg/max buckets. |
| get_problem_eventsB | Problem events (including resolved ones) in a time window, newest first. |
| acknowledge_problemB | Acknowledge, comment on, re-rate or close problems. Two-step: first call returns a preview. |
| manage_maintenance_windowB | List, schedule (one-time) or remove maintenance windows. create/delete are two-step. |
| get_sla_reportA | SLA/SLI per service for recent periods; without 'sla' lists available SLAs. |
| get_audit_logB | Zabbix audit log entries (who changed what), newest first. |
| get_server_statusB | Zabbix version, HA nodes, proxies, host counts and open problem counts. |
| dashboard_widget_catalogA | Supported dashboard widget types with their key field names, plus layout rules. |
| manage_dashboardC | Create and edit Zabbix dashboards. Changes are validated, then two-step confirmed. |
| zabbix_search_methodsB | Find Zabbix 7.4 API methods by name. Shows which tool runs each and if it is allowed. |
| zabbix_describe_methodA | Docs link, read/write class, permission status and usage tips for one API method. |
| zabbix_raw_apiA | Escape hatch: call any 7.4 API method. Same safety rules (read-only, blocklist, confirmation). |
| zabbix_monitoringA | Zabbix monitoring API. Methods: problem: get; event: acknowledge, get; alert: get; trigger: create, delete, get, update; history: clear, get, push; trend: get; item: create, delete, get, update; graph: create, delete, get, update; graphitem: get; hanode: get; task: create, get; auditlog: get. Reads return compact defaults; writes are two-step (preview, then repeat with confirm_token). Use zabbix_describe_method for docs and parameters. |
| zabbix_hostsA | Zabbix hosts API. Methods: host: create, delete, get, massadd, massremove, massupdate, update; hostgroup: create, delete, get, massadd, massremove, massupdate, propagate, update; hostinterface: create, delete, get, massadd, massremove, replacehostinterfaces, update; template: create, delete, get, massadd, massremove, massupdate, update; templategroup: create, delete, get, massadd, massremove, massupdate, propagate, update; proxy: create, delete, get, update; proxygroup: create, delete, get, update; maintenance: create, delete, get, update. Reads return compact defaults; writes are two-step (preview, then repeat with confirm_token). Use zabbix_describe_method for docs and parameters. |
| zabbix_configA | Zabbix config API. Methods: itemprototype: create, delete, get, update; triggerprototype: create, delete, get, update; graphprototype: create, delete, get, update; hostprototype: create, delete, get, update; discoveryrule: create, delete, get, update; discoveryruleprototype: create, delete, get, update; drule: create, delete, get, update; dhost: get; dservice: get; dcheck: get; httptest: create, delete, get, update; httpstep: get; usermacro: create, createglobal, delete, deleteglobal, get, update, updateglobal; valuemap: create, delete, get, update; regexp: create, delete, get, update; correlation: create, delete, get, update; configuration: export, import, importcompare. Reads return compact defaults; writes are two-step (preview, then repeat with confirm_token). Use zabbix_describe_method for docs and parameters. |
| zabbix_visualizationA | Zabbix visualization API. Methods: dashboard: create, delete, get, update; templatedashboard: create, delete, get, update; map: create, delete, get, update; iconmap: create, delete, get, update; image: create, delete, get, update; report: create, delete, get, update. Reads return compact defaults; writes are two-step (preview, then repeat with confirm_token). Use zabbix_describe_method for docs and parameters. |
| zabbix_servicesA | Zabbix services API. Methods: service: create, delete, get, update; sla: create, delete, get, getsli, update. Reads return compact defaults; writes are two-step (preview, then repeat with confirm_token). Use zabbix_describe_method for docs and parameters. |
| zabbix_alertingA | Zabbix alerting API. Methods: action: create, delete, get, update; mediatype: create, delete, get, update; script: create, delete, execute, get, getscriptsbyevents, getscriptsbyhosts, update; connector: create, delete, get, update. Reads return compact defaults; writes are two-step (preview, then repeat with confirm_token). Use zabbix_describe_method for docs and parameters. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_problems | Triage current Zabbix problems and propose next steps |
| host_health_check | Health check for one host |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
The curated convenience tools (get_active_problems, get_problem_events, get_triggers, get_audit_log, manage_dashboard, get_sla_report) overlap directly with the generic grouped tools (zabbix_monitoring, zabbix_visualization, zabbix_services), so an agent must guess whether to use the wrapper or the raw group call. Descriptions hint at the distinction (compact curated reads vs full API surface), but boundaries remain fuzzy for several pairs.
Naming mixes several conventions: verb_noun wrappers (get_problem_events, search_hosts, acknowledge_problem), a zabbix_ namespace prefix (zabbix_monitoring, zabbix_raw_api, zabbix_describe_method), manage_ verbs (manage_dashboard, manage_maintenance_window), and a bare noun (dashboard_widget_catalog). Each name is readable on its own, but there is no single predictable pattern an agent can rely on.
24 tools lands at the borderline-heavy end of the scale, and some of that weight is redundant since the six grouped API tools already subsume much of what the convenience wrappers do. Given Zabbix's very large API surface the count is defensible, but it is not tightly scoped.
Coverage is broad: monitoring, hosts, config, visualization, services, alerting, docs lookup and a raw API escape hatch cover nearly every lifecycle operation, including two-step writes. Minor gaps exist (e.g. user/usergroup/role and token management APIs are not exposed), but agents can work around these via zabbix_raw_api.