Zabbix MCP Server
Zabbix MCP Server exposes Zabbix monitoring and operations capabilities to MCP-compatible AI clients via 21 focused tools, with optional read-only mode and HTTP/stdio transports.
Query hosts, host groups, hosts in groups, host-by-IP, and host software inventory.
Update a host's visible name and host group membership, subject to read-only/tool-denial controls.
Query monitored items and triggers, including semantic search, key-metric filtering, and severity filters.
Retrieve raw item history, hourly trend data, and sample-weighted trend summaries with coverage/volatility metrics.
Query raw historical events with cursor pagination, and inspect current problems via unified summaries and per-event fact details such as recovery, manual handling, and monitoring status.
Check overall status, per-host health, interface availability, classified problems, key metrics, and paired alert/recovery history.
Generate daily, weekly, and monthly Markdown operations reports, optionally production-only and with configurable section sizes.
Get Zabbix API version information.
Apply operational/security controls such as read-only mode, denied tools, response-size limits, SSL verification, and HTTP source-IP allowlisting.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Zabbix MCP ServerSummarize the current problems and their severities."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Zabbix MCP Server
English | 中文文档
A Model Context Protocol (MCP) server for Zabbix integration using FastMCP and python-zabbix-utils. It ships 21 focused tools for querying hosts, items, triggers, problems and monitoring data, plus daily/weekly/monthly operations report generators — designed for AI-assisted operations (AIOps) agents.
Features
🏠 Host Management
host_get- Query hosts with filtering, group/template selection and inventoryhost_update- Update a host's visible name and host groupsget_host_by_ip- Look up a host precisely by its IP addresshostgroup_get- Query host groupshostgroup_get_hosts- List hosts inside one or more host groupshost_software_inventory_get- Query a single host's software inventory
📊 Monitoring Data
item_get- Query items with semantic search and key-metric filteringtrigger_get- Query triggers, optionally filtered by severityhistory_get- Get raw item history datatrend_get- Get hourly-aggregated trend datatrend_summary- Sample-weighted trend summary over a time window
🚨 Problems & Events
event_get- Query raw historical events with cursor paginationget_problem_summary- Unified classification summary of current problemsget_problem_fact_detail- Real recovery, manual handling and current monitoring status per problem eventquick_status- Overall status: hosts, classified problems and last-24h eventscheck_host_health- Per-host interface availability, problem classification and key metricshost_alert_history- Fully paired alert/recovery history per host and trigger
📈 Operations Reports
event_daily_report- Generate a daily operations report in Markdownevent_weekly_report- Generate a weekly (Mon–Sun) operations reportevent_monthly_report- Generate a monthly operations report
ℹ️ System
apiinfo_version- Get the Zabbix API version
Related MCP server: Zabbix MCP Server
Installation
Prerequisites
Python 3.10 or higher
uv package manager
Access to a Zabbix server with API enabled
Quick Start
Clone the repository:
git clone https://github.com/TemplarFan/zabbix-mcp-server.git cd zabbix-mcp-serverInstall dependencies:
uv syncConfigure environment variables:
cp config/.env.example .env # Edit .env with your Zabbix server detailsTest the installation:
uv run python scripts/test_server.py
Configuration
Required Environment Variables
ZABBIX_URL- Your Zabbix server API endpoint (e.g.,https://zabbix.example.com)
Authentication (choose one method)
Method 1: API Token (Recommended)
ZABBIX_TOKEN- Your Zabbix API token
Method 2: Username/Password
ZABBIX_USER- Your Zabbix usernameZABBIX_PASSWORD- Your Zabbix password
Optional Configuration
READ_ONLY- Set totrue,1, oryesto enable read-only mode (only GET operations allowed)VERIFY_SSL- Enable/disable SSL certificate verification (default:true)ZABBIX_TEST_NETWORKS- Comma-separated test network CIDRs (e.g.,192.168.100.0/24,192.168.101.0/24) excluded by report tools whenproduction_only=true; leave empty to disableZABBIX_MAX_RESPONSE_CHARS- Max characters per tool response (default:50000); oversized list results are truncated per entry (JSON stays valid) with an envelope and narrowing adviceZABBIX_DENY_TOOLS- Comma-separated tool names removed at registration (invisible to models, e.g.,host_update); leave empty to enable all toolsZABBIX_ALLOWED_IPS- Comma-separated source IPs/CIDRs allowed on the HTTP transport (e.g.,127.0.0.1,192.168.0.0/16); unmatched sources get403; leave empty to allow all (stdio is unaffected)
Transport Configuration
ZABBIX_MCP_TRANSPORT- Transport type:stdio(default) orstreamable-http
HTTP Transport Configuration (only used when ZABBIX_MCP_TRANSPORT=streamable-http):
ZABBIX_MCP_HOST- Server host (default:127.0.0.1)ZABBIX_MCP_PORT- Server port (default:8000)ZABBIX_MCP_STATELESS_HTTP- Stateless mode (default:false)AUTH_TYPE- Must be set tono-authfor streamable-http transport
Usage
Running the Server
With startup script (recommended):
uv run python scripts/start_server.pyDirect execution:
uv run python -m src.mainTransport Options
The server supports two transport methods:
STDIO Transport (Default)
Standard input/output transport for MCP clients like Claude Desktop:
# Set in .env or environment
ZABBIX_MCP_TRANSPORT=stdioHTTP Transport
HTTP-based transport for web integrations:
# Set in .env or environment
ZABBIX_MCP_TRANSPORT=streamable-http
ZABBIX_MCP_HOST=127.0.0.1
ZABBIX_MCP_PORT=8000
ZABBIX_MCP_STATELESS_HTTP=false
AUTH_TYPE=no-authNote: When using streamable-http transport, AUTH_TYPE must be set to no-auth.
Testing
Run test suite:
uv run python scripts/test_server.pyRead-Only Mode
When READ_ONLY=true, the server will only expose GET operations (retrieve data) and block all create, update, and delete operations. This is useful for:
📊 Monitoring dashboards
🔍 Read-only integrations
🔒 Security-conscious environments
🛡️ Preventing accidental modifications
Example Tool Calls
Get all hosts:
host_get()Get hosts in specific group:
host_get(groupids=["1"])Summarize current problems needing attention:
get_problem_summary(view="actionable")Get history data:
history_get(
itemids=["12345"],
time_from="24h",
limit=100
)Check a host's health:
check_host_health(host_identifier="web-server-01")Generate yesterday's operations report:
event_daily_report(date="yesterday", production_only=true)MCP Integration
This server is designed to work with MCP-compatible clients like Claude Desktop. See MCP_SETUP.md for detailed integration instructions.
Development
Project Structure
zabbix-mcp-server/
├── src/ # MCP server implementation
│ ├── main.py # Server entrypoint and tool registration
│ ├── client.py # Zabbix API client
│ ├── config.py # Configurable parameters
│ ├── tools/ # MCP tool definitions
│ ├── reporting/ # Daily/weekly/monthly report generators
│ ├── services/ # Business logic services
│ └── utils/ # Helpers
├── scripts/
│ ├── start_server.py # Startup script with validation
│ └── test_server.py # Test script
├── config/
│ ├── .env.example # Environment configuration template
│ ├── mcp.json # MCP client configuration example
│ └── workflow_prompt.md # Alarm analysis workflow prompt
├── .env.example # Environment configuration template
├── pyproject.toml # Python project configuration
├── requirements.txt # Dependencies
├── uv.lock # Lockfile for reproducible installs
├── README.md # This file
├── README.zh-CN.md # Chinese documentation
├── MCP_SETUP.md # MCP integration guide
└── LICENSE # GPL-3.0 licenseContributing
Fork the repository
Create a feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
Running Tests
# Test server functionality
uv run python scripts/test_server.pyError Handling
The server includes comprehensive error handling:
✅ Authentication errors are clearly reported
🔒 Read-only mode violations are blocked with descriptive messages
✔️ Invalid parameters are validated
🌐 Network and API errors are properly formatted
📝 Detailed logging for troubleshooting
Security Considerations
🔑 Use API tokens instead of username/password when possible
🔒 Enable read-only mode for monitoring-only use cases
🛡️ Secure your environment variables
🔐 Use HTTPS for Zabbix server connections
🔄 Regularly rotate API tokens
📁 Store configuration files securely
Troubleshooting
Common Issues
Connection Failed:
Verify
ZABBIX_URLis correct and accessibleCheck authentication credentials
Ensure Zabbix API is enabled
Permission Denied:
Verify user has sufficient Zabbix permissions
Check if read-only mode is enabled when trying to modify data
Tool Not Found:
Ensure all dependencies are installed:
uv syncVerify Python version compatibility (3.10+)
Debug Mode
Set environment variable for detailed logging:
export DEBUG=1
uv run python scripts/start_server.pyDependencies
FastMCP - MCP server framework
python-zabbix-utils - Official Zabbix Python library
License
This project is licensed under the GNU General Public License v3.0 - see the LICENSE file for details.
Project Origin
Based on mpeirone/zabbix-mcp-server (GPL-3.0). This project has been substantially rewritten and extended with:
Operations report generators (daily / weekly / monthly) with unified problem classification
Problem fact-checking service (true recovery and manual handling status)
Production-only filtering driven by environment configuration
Alarm-analysis prompt template for n8n workflows
A fully documented 21-tool MCP toolset aligned with the actual implementation
Acknowledgments
Zabbix for the monitoring platform
Model Context Protocol for the integration standard
FastMCP for the server framework
Made with ❤️ for the Zabbix and MCP communities
Available Tools
21 toolsapiinfo_versionA
获取Zabbix API版本信息
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
check_host_healthA
按主机查询接口可用性、统一当前问题分类和关键指标。
| Name | Required | Description | Default |
|---|---|---|---|
| time_range | No | 告警时间范围(默认24h) | 24h |
| trend_hours | No | 趋势数据查询时长 | |
| include_oracle | No | 是否查询Oracle相关指标 | |
| include_trends | No | 是否包含趋势数据 | |
| host_identifier | Yes | 主机标识(IP/主机名/hostid) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
event_daily_reportA
生成运维日报 Markdown,展示条数默认与定时推送日报一致,可按章节覆盖或仅统计生产口径。
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | 日报日期,支持 yesterday 或 YYYY-MM-DD,默认 yesterday | yesterday |
| top_n_severe | No | 严重事件中严重子章节展示条数(>0前N条/0跳过章节/-1全部展示,默认-1) | |
| top_n_chronic | No | 持续型问题章节展示条数(>0前N条/0跳过章节/-1全部展示,默认-1) | |
| top_n_disaster | No | 严重事件中灾难子章节展示条数(>0前N条/0跳过章节/-1全部展示,默认-1) | |
| production_only | No | 是否仅统计生产口径,排除配置的测试网段(ZABBIX_TEST_NETWORKS)主机(默认False) | |
| top_n_high_frequency | No | 高频报警主机章节展示条数(>0前N条/0跳过章节/-1全部展示,默认20) | |
| top_n_short_recovery | No | 短时恢复型问题章节展示条数(>0前N条/0跳过章节/-1全部展示,默认-1) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
event_getA
查询原始历史事件;业务状态解释使用问题事实明细工具。
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 最终返回数量(默认10,不是候选扫描上限) | |
| value | No | 本地筛选事件状态(1问题发生/0恢复) | |
| output | No | 返回字段列表 | |
| source | No | 事件来源(默认0触发器事件) | |
| hostids | No | 主机ID | |
| object_ | No | 事件对象类型 | |
| eventids | No | 事件ID | |
| groupids | No | 群组ID筛选 | |
| objectids | No | 触发器ID | |
| time_from | No | 起始时间(支持7d/24h或Unix时间戳) | |
| time_till | No | 截止时间(支持相对时间或Unix时间戳) | |
| severities | No | 严重级别列表 | |
| eventid_till | No | 下一页事件ID游标;首次查询不传 |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
event_monthly_reportB
生成运维月报 Markdown,展示条数默认与定时推送月报一致,可按章节覆盖或仅统计生产口径。
| Name | Required | Description | Default |
|---|---|---|---|
| month | No | 月报月份,支持 last_month 或 YYYY-MM,默认 last_month | last_month |
| top_n_severe | No | 严重事件中严重子章节展示条数(>0前N条/0跳过章节/-1全部展示,默认10) | |
| top_n_chronic | No | 持续型问题章节展示条数(>0前N条/0跳过章节/-1全部展示,默认10) | |
| top_n_regular | No | 规律型问题章节展示条数(>0前N条/0跳过章节/-1全部展示,默认5) | |
| top_n_disaster | No | 严重事件中灾难子章节展示条数(>0前N条/0跳过章节/-1全部展示,默认5) | |
| production_only | No | 是否仅统计生产口径,排除配置的测试网段(ZABBIX_TEST_NETWORKS)主机(默认False) | |
| top_n_high_frequency | No | 高频报警主机章节展示条数(>0前N条/0跳过章节/-1全部展示,默认10) | |
| top_n_short_recovery | No | 短时恢复型问题章节展示条数(>0前N条/0跳过章节/-1全部展示,默认5) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
event_weekly_reportA
生成周一至周日运维周报 Markdown,展示条数默认与定时推送周报一致,可按章节覆盖或仅统计生产口径。
| Name | Required | Description | Default |
|---|---|---|---|
| week | No | 周内任意日期,支持 last_week 或 YYYY-MM-DD,默认 last_week | last_week |
| top_n_severe | No | 严重事件中严重子章节展示条数(>0前N条/0跳过章节/-1全部展示,默认-1) | |
| top_n_chronic | No | 持续型问题章节展示条数(>0前N条/0跳过章节/-1全部展示,默认10) | |
| top_n_regular | No | 规律型问题章节展示条数(>0前N条/0跳过章节/-1全部展示,默认10) | |
| top_n_disaster | No | 严重事件中灾难子章节展示条数(>0前N条/0跳过章节/-1全部展示,默认-1) | |
| production_only | No | 是否仅统计生产口径,排除配置的测试网段(ZABBIX_TEST_NETWORKS)主机(默认False) | |
| top_n_high_frequency | No | 高频报警主机章节展示条数(>0前N条/0跳过章节/-1全部展示,默认15) | |
| top_n_short_recovery | No | 短时恢复型问题章节展示条数(>0前N条/0跳过章节/-1全部展示,默认5) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_host_by_ipA
通过IP精确查询主机。已知IP时优先用此工具,比host_get更精准省Token
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes | 主机IP地址 |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_problem_fact_detailA
按问题事件 ID 查询真实恢复、人工处置和当前监控状态。
| Name | Required | Description | Default |
|---|---|---|---|
| eventid | Yes | 问题事件ID(不是触发器ID) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_problem_summaryA
查询统一分类后的当前问题摘要。历史事件用event_get
| Name | Required | Description | Default |
|---|---|---|---|
| view | No | 查询视图:current当前仍在触发分组、actionable当前需处理、handled_active已处置但仍触发 | current |
| hostids | No | 主机ID(不支持主机名,需先查host_get) | |
| group_by | No | 明细分组方式:severity或host | severity |
| time_range | No | 可选时间范围;不传时查询全部原始当前问题,传入7d/24h等时只筛选开始时间 |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
history_getA
获取监控项原始历史数据。长期趋势用trend_get
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 返回条数(默认10) | |
| history | No | 数据类型(0float/1char/2log/3uint/4text) | |
| itemids | Yes | 监控项ID(必填) | |
| sortfield | No | 排序字段(默认clock) | clock |
| sortorder | No | 排序方向(DESC/ASC) | DESC |
| time_from | No | 起始时间(支持相对时间如7d/24h) | |
| time_till | No | 截止时间 |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
host_alert_historyC
查询完整分页、精确恢复配对的主机与触发器告警历史。
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | 查询天数(默认7) | |
| hostid | Yes | 主机ID | |
| triggerid | Yes | 触发器ID |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | 查询失败原因 |
| complete | Yes | 查询及补齐是否完整 |
| host_summary | Yes | 主机概览(查询期间主机所有告警统计) |
| alerts_before | Yes | 当前告警前的其他告警(可能关联) |
| trigger_stats | Yes | 当前触发器统计(历史告警分析) |
host_getB
查询主机列表。支持ID精确查询或名称模糊匹配,已知IP时优先用get_host_by_ip
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | 主机名关键词,模糊匹配 | |
| limit | No | 返回数量(默认10) | |
| filter | No | 精确过滤条件 | |
| output | No | 返回字段列表 | |
| search | No | 搜索条件字典 | |
| hostids | No | 主机ID(单个或逗号分隔多个) | |
| groupids | No | 主机组ID筛选 | |
| templateids | No | 模板ID筛选 | |
| selectGroups | No | 是否返回主机所属群组信息 | |
| selectInventory | No | 是否返回主机资产信息 |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
hostgroup_getC
查询主机群组列表
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | 群组名称关键词(模糊搜索) | |
| limit | No | 返回数量(默认50) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
hostgroup_get_hostsA
查询群组内的主机列表。需先通过hostgroup_get获取groupid
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 返回数量(默认50) | |
| groupids | Yes | 群组ID(单个或逗号分隔多个) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
host_software_inventory_getB
查询单台主机的软件资产信息(software/software_full/software_app_a-e)
| Name | Required | Description | Default |
|---|---|---|---|
| host_identifier | Yes | 主机标识(hostid/IP地址/主机名) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
host_updateA
修改主机的可见名称和群组。群组参数为groupid(需先查询)
| Name | Required | Description | Default |
|---|---|---|---|
| hostid | Yes | 主机ID | |
| new_name | No | 新可见名称 | |
| add_groups | No | 要添加的群组ID(追加模式) | |
| remove_groups | No | 要移除的群组ID |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
item_getA
查询监控项。需先通过host_get获取hostid。支持语义搜索,key_metrics_only智能筛选最佳指标
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 返回数量(默认20) | |
| output | No | 返回字段列表 | |
| search | No | 搜索关键词或条件字典(支持语义搜索如memory/cpu) | |
| hostids | No | 主机ID | |
| itemids | No | 监控项ID | |
| key_metrics_only | No | 仅返回关键性能指标(CPU/内存/磁盘),每类最多1个 |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
quick_statusC
查看主机、统一当前问题分类及最近二十四小时事件。
| Name | Required | Description | Default |
|---|---|---|---|
| include_offline | No | 列出离线主机列表(默认True) | |
| include_disabled | No | 列出停用主机列表(默认False,只显示统计数字) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
trend_getA
获取监控项趋势数据(每小时聚合)。摘要用trend_summary
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 返回条数(默认24) | |
| itemids | Yes | 监控项ID(必填) | |
| time_from | No | 起始时间(支持相对时间如7d) | |
| time_till | No | 截止时间 |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
trend_summaryB
按趋势桶样本数加权汇总,并返回时间桶与样本覆盖情况。
| Name | Required | Description | Default |
|---|---|---|---|
| hours | No | 查询时长。建议:磁盘168h、内存72h、CPU24h、网络48h | |
| itemids | Yes | 监控项ID(最多3个) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
trigger_getB
查询触发器列表。priority=3,4,5只看严重以上级别
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 返回数量(默认20) | |
| filter | No | 精确过滤条件 | |
| output | No | 返回字段列表 | |
| search | No | 搜索条件 | |
| hostids | No | 主机ID筛选 | |
| groupids | No | 群组ID筛选 | |
| priority | No | 严重级别(0未分类/1信息/2警告/3一般/4严重/5灾难) | |
| triggerids | No | 触发器ID | |
| templateids | No | 模板ID筛选 | |
| include_expression | No | 是否返回触发表达式(默认False节省Token) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- Changed
get_problem_summary1 field changed- changed
Input schema / properties / view / descriptionPrevious value: -"查询视图:current当前仍在触发分组、actionable当前需处理、handled_active已处置但仍触发、indeterminate不可判定"New value: +"查询视图:current当前仍在触发分组、actionable当前需处理、handled_active已处置但仍触发"
21 tool updates
v1.1.0- First observed
apiinfo_version - First observed
check_host_health - First observed
event_daily_report - First observed
event_get - First observed
event_monthly_report - First observed
event_weekly_report - First observed
get_host_by_ip - First observed
get_problem_fact_detail - First observed
get_problem_summary - First observed
history_get - First observed
host_alert_history - First observed
host_get - First observed
host_software_inventory_get - First observed
host_update - First observed
hostgroup_get - First observed
hostgroup_get_hosts - First observed
item_get - First observed
quick_status - First observed
trend_get - First observed
trend_summary - First observed
trigger_get
TDQS
Scored across 21 tools
Several read-oriented tools overlap around current problems, host health, quick status, and event history: get_problem_summary, get_problem_fact_detail, check_host_health, quick_status, host_alert_history, and event_get can be confused despite their descriptions. The descriptions do provide guidance, but boundaries are not always crisp.
All names use snake_case, but verb/noun ordering is mixed: host_get, item_get, event_get, and trend_get use noun_verb, while get_problem_summary, get_host_by_ip, and check_host_health use verb_noun, and others like quick_status and apiinfo_version are noun phrases. The conventions are readable but inconsistent.
21 tools is on the heavy side, but Zabbix is a broad monitoring domain covering hosts, groups, items, triggers, events, history, trends, reports, and health checks. Most tools map to distinct data needs, though a few status/problem tools could be consolidated.
The read surface is strong: hosts, groups, software inventory, items, triggers, events, history, trends, health checks, and daily/weekly/monthly reports are covered. Write/lifecycle coverage is thinner, with host_update but no host create/delete, problem acknowledgement, maintenance, or template/user management, which are notable but not fatal for a query/report-focused server.
Maintenance
Related MCP Connectors
Connect AI assistants to Xitoring monitoring: servers, uptime, incidents, metrics, SSL, and alerts.
Manage uptime monitors and incidents and search logs, metrics and traces from an AI assistant.
Monitors TLS/SSL certificate expiry, DNS resolution, and TCP port status for AI agents.
Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
Related MCP Servers
- AlicenseAqualityDmaintenance🔌 Complete MCP server for Zabbix integration - Connect AI assistants to Zabbix monitoring with 40+ tools for hosts, items, triggers, templates, problems, and more. Features read-only mode and comprehensive API coverage.3260GPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables users to monitor and query Zabbix infrastructure through natural language by providing access to current problems, active triggers, and system health status via the Zabbix API.-
- AlicenseBqualityAmaintenanceOfficial initMAX MCP server exposing the Zabbix API to AI assistants for monitoring and managing hosts, problems, templates, dashboards, and multiple Zabbix instances. Includes correlated monitoring views, graphs, anomaly detection, capacity forecasts, and PDF reports, with scoped tokens, read-only modes, OAuth 2.1, and an admin portal. Supports Streamable HTTP, SSE, and stdio.84247AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceExposes Zabbix monitoring capabilities as callable tools for AI agents and MCP-compatible clients.-