Task-shaped Zabbix access for AI agents: problems, host triage, metrics, maintenance windows.
MCPpedia last refreshed this data
io.github.stufently/zabbix-ai-cli-mcp is an MCP server that task-shaped Zabbix access for AI agents: problems, host triage, metrics, maintenance windows. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 75/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"zabbix": {
"args": [
"mcp",
"--profile",
"prod"
],
"command": "zabbix-ai-cli-mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Task-shaped Zabbix access for AI agents: problems, host triage, metrics, maintenance windows.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ai-ml / analytics
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
An open-source AI agent that brings the power of Gemini directly into your terminal.
🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.
MCP Security Weekly
Get CVE alerts and security updates for io.github.stufently/zabbix-ai-cli-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
zabbix-ai-cli-mcp is a Zabbix MCP server and command-line client in one Go
binary. It gives Claude Code, Claude Desktop, Codex, Cursor and any other
Model Context Protocol client task-shaped access to Zabbix — what is broken
right now, why a host is silent, why an alert never arrived — with bounded
output, a stable JSON contract, and one setting, allow_write, that decides
whether the agent applies a change or a person approves a plan.
It is for the people who get paged: SRE and DevOps teams running Zabbix who want an agent to triage an incident without handing it the whole API.
Requires Zabbix 6.4 or newer. Bearer-token authentication arrived in 6.4 and is the only scheme implemented; earlier versions expect the token in the request body instead.
It never contacts a language model. The AI decides, this program executes, Zabbix monitors.
zabbix-ai-cli-mcp login
zabbix-ai-cli-mcp problems list
zabbix-ai-cli-mcp host investigate server01
zabbix-ai-cli-mcp alert why 757474
zabbix-ai-cli-mcp mcp
Wrapping host.get, problem.get and history.get hands the agent the API's
sharp edges along with its power. On a current Zabbix 7.4 server:
problem.get has no selectHosts, so a problem list arrives without hosts.history.get defaults to the numeric-unsigned table and returns nothing for
a float item — silently, with no error.item.lastvalue and item.lastclock still exist and have returned a constant
"0" for several major releases.host.available was removed in 5.4; availability lives on the interface.event.acknowledge takes a bitmask whose own documentation contradicts itself.searchWildcardsEnabled: true disables implicit substring matching, turning
a name fragment into an exact match that quietly finds nothing.Every one of those produces a confident, wrong answer rather than an error. This tool absorbs them behind commands that describe the task instead of the endpoint.
| Command | Answers |
|---|---|
problems list | What is broken now — including suppressed problems, with the maintenance window that hides them named |
host investigate | One call: host state, active problems, recent events, silent and unsupported items, maintenance |
host status | A handful of fields instead of twelve thousand characters of configuration |
alert why | Why a notification did or did not arrive — suppression, delivery attempts, actions, media types, per-recipient severity filters |
resolve | Turns a notification pasted out of chat into event, host and trigger identifiers |
unreachable | Monitored hosts Zabbix cannot poll, with the error it recorded |
metrics latest / history | Values with the right history type, human units and min/avg/max |
maintenance | Open, extend, end or remove windows, with host patterns like ms* |
mediatypes enable / disable | Restore or stop alert delivery by changing only a media type's status |
discoveryrules set-lost-resources | Adjust lost LLD resource disable/delete policy with an impact plan |
api call | The escape hatch, under the same rules |
Read operations always run immediately. Whether anything else does is one
setting, allow_write, and it is on by default.
# ~/.config/zabbix-ai-cli-
... [View full README on GitHub](https://github.com/stufently/zabbix-ai-cli-mcp#readme)