$ loading_
Access Zabbix API via MCP for monitoring, reports, and alerts.
This is an open-source GitHub MCP server whose stated purpose is to interface with the full Zabbix API and it has local code-execution capability. No explicit malicious or abnormal exfiltration red flags are shown, but its broad API surface, likely Zabbix connectivity, and limited documentation justify an overall caution rating.
The header says no keys/environment variables are required, yet the description claims support for 'OAuth 2.1 + bearer auth,' indicating it will likely handle Zabbix credentials or access tokens in real use. There is no stated guidance on token storage, encryption, or least privilege, so normal credential exposure and misconfiguration risks remain.
No remote endpoint is listed in the header, but the stated 'complete Zabbix API' and multi-server support imply outbound connections to one or more Zabbix servers. The provided material does not show data being sent to unrelated third-party endpoints or suspicious exfiltration; the main concern is routine network interaction with intended monitoring servers.
The system checks confirm this tool has code-execution capability, and as an MCP server it normally runs as a local process. The available material does not indicate requests for system privileges beyond its stated function, nor does it explicitly describe arbitrary shell/script execution, so this remains caution as an inherent tool capability.
Its claims of '237 tools,' 'complete Zabbix API,' and 'PDF reports' suggest potentially broad access to Zabbix data such as monitored assets, alerts, topology, and reports, and possible local report-file generation. There is no evidence of broad filesystem access or unrelated data collection, but the API surface is extensive and should be constrained with least privilege.
The source is a GitHub open-source repository under AGPL-3.0, making it auditable, and it has some community adoption (121 stars), all of which reduce risk. The main gaps are the missing README and unknown maintenance status, which reduce transparency and increase dependency-review effort, but the current facts do not justify a high-risk rating.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "zabbix-mcp-server" yet — see the docs or source repo.
Use the Zabbix MCP to list all unresolved problems, sort by severity, and summarize the top 5 urgent ones.
A ranked list of unresolved problems with a brief priority summary.
Generate a PDF monitoring report from the last 24 hours of Zabbix data, including availability, alert stats, and trend overview.
A downloadable PDF report or a concise summary of the generated report contents.
List the key hosts on the specified Zabbix server and their active triggers, highlighting anomalies.
Host and trigger status with anomalies or high-risk items clearly highlighted.
Connect to Zabbix for monitoring, alert handling, and infrastructure management.
Turn Zabbix monitoring into callable tools for alerts, hosts, and metrics.
Access Zabbix data to inspect hosts, alerts, items, and event history.
Access Zabbix monitoring briefs, problems, hosts, and items via API.
Automate Zalo personal and official accounts through MCP for AI-driven workflows.
Turn existing APIs and databases into MCP tools for direct AI use.