Zabbix MCP (Mhajder)

MCPAI代理

提供方 未标注

AI代理 SSE · 服务端推送 Token 社区 / 第三方
查看接入方式

全面解析Zabbix MCPMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,Zabbix MCP能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

Zabbix MCP (Mhajder) 属于AI代理类 MCP 服务器,SSE · 服务端推送,Token,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式SSE · 服务端推送 鉴权Token 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

SSE · 服务端推送 Token
早期远程传输方式,正在被 HTTP 取代
pip install zabbix-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zabbix MCP (Mhajder)当前 未标注 SSE · 服务端推送 远程部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式SSE · 服务端推送早期远程传输方式,正在被 HTTP 取代
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

15.8 KB
来自项目仓库与上游目录的原文,未做删改

Zabbix MCP Server

Let AI agents query and manage Zabbix monitoring through the Model Context Protocol

Installation · Tools · Configuration · Security

Zabbix MCP Server is a Python-based Model Context Protocol (MCP) server designed to provide advanced, programmable access to Zabbix monitoring data and management features. It exposes a modern API for querying, automating, and integrating Zabbix resources such as hosts, templates, triggers, items, problems, events, users, proxies, maintenance periods, and more. The server supports both read and write operations, robust security features, and is suitable for integration with AI assistants, automation tools, dashboards, and custom monitoring workflows.

✨ Features

Core Features

  • Query Zabbix hosts, templates, items, triggers, and host groups with flexible filtering
  • Retrieve problems, events, and alerts with severity filtering
  • Access history and trend data for monitored items
  • Monitor trigger states and problem severity
  • Manage maintenance periods and scheduled downtimes
  • Retrieve user macros and configuration data
  • Get SLA and service information

Management Operations

  • Create, update, and delete hosts, templates, and host groups (if enabled)
  • Manage triggers, items, and discovery rules
  • Configure maintenance periods and user macros
  • Execute scripts on monitored hosts
  • Acknowledge events and close problems
  • Create and manage users and proxies
  • Support for bulk operations on hosts and templates

Advanced Capabilities

  • Rate limiting and API security features
  • Read-only mode to restrict all write operations for safe monitoring
  • Optional tool-search transform for large tool catalogs
  • Bearer token authentication for HTTP transport
  • Comprehensive logging and audit trails
  • SSL/TLS support and configurable timeouts
  • Multiple transport options (STDIO, SSE, HTTP)
  • Optional Sentry integration for error tracking

🚀 Installation

Prerequisites

  • Python 3.11 to 3.15
  • Access to a Zabbix server. Versions 6.0 to 7.4 are supported - that is the range
    the zabbix-utils client accepts, and it refuses to connect outside it unless
    ZABBIX_SKIP_VERSION_CHECK=true is set
  • Valid Zabbix API token or user credentials with appropriate permissions

Quick Install from PyPI

The easiest way to get started is to install from PyPI:```sh

Using UV (recommended)

uvx zabbix-mcp

Or using pip

pip install zabbix-mcp


Remember to configure the environment variables for your Zabbix instance before running the server:```sh
# Create environment configuration
export ZABBIX_URL=https://zabbix.example.com/api_jsonrpc.php
export ZABBIX_TOKEN=your-zabbix-api-token

Install from Source

  1. Clone the repository:```sh
    git clone https://github.com/mhajder/zabbix-mcp.git
    cd zabbix-mcp

2. Install dependencies:```sh
# Using UV (recommended)
uv sync

# Or using pip
pip install -e .
  1. Configure environment variables:```sh
    cp .env.example .env

Edit .env with your Zabbix URL and credentials


4. Run the server:```sh
# Using UV (recommended)
uv run zabbix-mcp

# Or using the installed command directly
zabbix-mcp

Using Docker

A Docker image is available on GitHub Packages for easy deployment. It runs the
HTTP Streamable transport on port 8000 (/mcp).```sh
docker pull ghcr.io/mhajder/zabbix-mcp:latest


#### Open WebUI

Open WebUI 0.6.31 and later connect to the image directly; the separate MCPO
image (`ghcr.io/mhajder/zabbix-mcpo`) is no longer published. In Open WebUI,
go to **Admin Settings > Integrations > External Tool Servers**, add a connection
of type **MCP (Streamable HTTP)** with the URL `http://:8000/mcp`, and set
Bearer authentication to your `MCP_HTTP_BEARER_TOKEN`.

### Development Setup

For development with additional tools:```sh
# Clone and install with development dependencies
git clone https://github.com/mhajder/zabbix-mcp.git
cd zabbix-mcp
uv sync --group dev

# Run tests
uv run pytest

# Run with coverage
uv run pytest --cov=src/

# Run linting and formatting
uv run ruff check .
uv run ruff format .

# Run type checking
uv run ty check .

# Setup prek hooks
uv run prek install

🔧 Configuration

Environment Variables```env

Zabbix Connection Details

ZABBIX_URL=https://zabbix.example.com/api_jsonrpc.php

Authentication - use EITHER token OR user/password

API Token (preferred over user/password)

ZABBIX_TOKEN=your-api-token

OR Username/Password (for older versions)

ZABBIX_USER=Admin

ZABBIX_PASSWORD=zabbix

SSL Configuration

ZABBIX_VERIFY_SSL=true
ZABBIX_TIMEOUT=30
ZABBIX_SKIP_VERSION_CHECK=false

Read-Only Mode

Set READ_ONLY_MODE true to disable all write operations (create, update, delete)

READ_ONLY_MODE=false

Disabled Tags

Comma-separated list of tags to disable tools for (empty by default)

Example: DISABLED_TAGS=host,user,maintenance

DISABLED_TAGS=

Logging Configuration

LOG_LEVEL=INFO

Rate Limiting

Set RATE_LIMIT_ENABLED true to enable rate limiting

RATE_LIMIT_ENABLED=false
RATE_LIMIT_MAX_REQUESTS=60
RATE_LIMIT_WINDOW_MINUTES=1

Tool Search Transform (Optional)

Set TOOL_SEARCH_ENABLED true to replace full tool listing with search tools

TOOL_SEARCH_ENABLED=false

Search strategy: bm25 (natural language) or regex (pattern matching)

TOOL_SEARCH_STRATEGY=bm25

Maximum number of matching tools returned by search_tools

TOOL_SEARCH_MAX_RESULTS=5

Sentry Error Tracking (Optional)

Set SENTRY_DSN to enable error tracking and performance monitoring

SENTRY_DSN=https://your-key@o12345.ingest.us.sentry.io/6789

Optional Sentry configuration

SENTRY_TRACES_SAMPLE_RATE=1.0

SENTRY_SEND_DEFAULT_PII=false

SENTRY_ENVIRONMENT=production

SENTRY_RELEASE=1.2.3

SENTRY_PROFILE_SESSION_SAMPLE_RATE=1.0

SENTRY_PROFILE_LIFECYCLE=trace

SENTRY_ENABLE_LOGS=true

MCP Transport Configuration

Transport type: 'stdio' (default), 'sse' (Server-Sent Events), or 'http' (HTTP Streamable)

'streamable-http' is accepted as an alias for 'http'. Any other value stops

the server at startup.

MCP_TRANSPORT=stdio

HTTP Transport Settings (used when MCP_TRANSPORT=sse or MCP_TRANSPORT=http)

Host to bind the HTTP server (default: 127.0.0.1)

MCP_HTTP_HOST=127.0.0.1

Port to bind the HTTP server (default: 8000)

MCP_HTTP_PORT=8000

Optional bearer token for authentication (leave empty for no auth)

MCP_HTTP_BEARER_TOKEN=


## 🧰 Available Tools

### API Information

- `api_version`: Get Zabbix API version information

### Host Management

- `host_get`: List hosts with optional filtering by groups, templates, proxies, and search criteria
- `host_create`: Create a new host with interfaces and template linking
- `host_update`: Update host properties (name, status, description)
- `host_delete`: Delete hosts by ID

### Host Group Management

- `hostgroup_get`: List host groups with optional filtering
- `hostgroup_create`: Create a new host group
- `hostgroup_update`: Update an existing host group's properties (name)
- `hostgroup_delete`: Delete host groups

### Template Management

- `template_get`: List templates with optional filtering
- `template_create`: Create a new template
- `template_update`: Update template properties (name, description)
- `template_delete`: Delete templates

### Item Management

- `item_get`: List items with optional filtering by hosts, groups, templates
- `item_create`: Create a new item on a host
- `item_update`: Update item properties (name, delay, units, description, status)
- `item_delete`: Delete items

### Trigger Management

- `trigger_get`: List triggers with severity and state filtering
- `trigger_create`: Create a new trigger with expression
- `trigger_update`: Update trigger properties (description, expression, priority, status, comments)
- `trigger_delete`: Delete triggers

### Problem & Event Management

- `problem_get`: Get current problems with severity and time filtering
- `event_get`: Get events with time range filtering
- `event_acknowledge`: Acknowledge events with optional messages

### History & Trends

- `history_get`: Get historical data for items
- `trend_get`: Get trend data for items

### User Management

- `user_get`: List users with optional filtering
- `user_create`: Create a new user
- `user_update`: Update user properties (name, surname, password, type)
- `user_delete`: Delete users

### Proxy Management

- `proxy_get`: List proxies with optional filtering
- `proxy_create`: Create a new proxy
- `proxy_update`: Update proxy properties (name, operating mode, description)
- `proxy_delete`: Delete proxies

### Maintenance Management

- `maintenance_get`: List maintenance periods
- `maintenance_create`: Create a new maintenance period
- `maintenance_update`: Update maintenance period properties (name, times, description)
- `maintenance_delete`: Delete maintenance periods

### Action & Media

- `action_get`: List actions (triggers, autoregistration, etc.)
- `mediatype_get`: List media types

### Graph & Discovery

- `graph_get`: List graphs with optional filtering
- `discoveryrule_get`: List LLD discovery rules
- `drule_get`: List network discovery rules
- `itemprototype_get`: Get item prototypes from discovery rules

### SLA & Services

- `sla_get`: List SLAs
- `service_get`: List services

### Scripts

- `script_get`: List scripts
- `script_execute`: Execute a script on a host

### User Macros

- `usermacro_get`: List user macros (host and global)
- `usermacro_create`: Create a host macro
- `usermacro_delete`: Delete host macros

### Configuration Management

- `configuration_export`: Export Zabbix configurations to JSON or XML
- `configuration_import`: Import Zabbix configurations from JSON or XML

## 🔒 Security & Safety Features

### Read-Only Mode

The server supports a read-only mode that disables all write operations for safe monitoring:```env
READ_ONLY_MODE=true

Tag-Based Tool Filtering

You can disable specific categories of tools by setting disabled tags:```env
DISABLED_TAGS=alert,bills


### Tool Search for Large Toolsets

FastMCP tool search can reduce prompt size for servers with many tools.
When enabled, `list_tools` returns two synthetic tools:

- `search_tools`: Finds matching tools and returns their full schemas
- `call_tool`: Executes any discovered tool by name

Enable it with:```env
TOOL_SEARCH_ENABLED=true
TOOL_SEARCH_STRATEGY=bm25      # bm25 or regex
TOOL_SEARCH_MAX_RESULTS=8      # optional, default is 5

bm25 supports natural language queries, while regex uses a regex
pattern input for deterministic matching.

Tool search respects existing visibility controls (read-only mode and
disabled tags).

Rate Limiting

The server supports rate limiting to control API usage and prevent abuse. If enabled, requests are limited per client using a sliding window algorithm.

Enable rate limiting by setting the following environment variables in your .env file:```env
RATE_LIMIT_ENABLED=true
RATE_LIMIT_MAX_REQUESTS=60 # Maximum requests allowed per window (default: 60)
RATE_LIMIT_WINDOW_MINUTES=1 # Window size in minutes


If `RATE_LIMIT_ENABLED` is set to `true`, the server will apply rate limiting middleware. Adjust `RATE_LIMIT_MAX_REQUESTS` and `RATE_LIMIT_WINDOW_MINUTES` as needed for your environment.

### Sentry Error Tracking & Monitoring (Optional)

The server optionally supports **Sentry** for error tracking, performance monitoring, and debugging. Sentry integration is completely optional and only initialized if configured.

#### Installation

To enable Sentry monitoring, install the optional dependency:```sh
# Using UV (recommended)
uv sync --extra sentry

Configuration

Enable Sentry by setting the SENTRY_DSN environment variable in your .env file:```env

Required: Sentry DSN for your project

SENTRY_DSN=https://your-key@o12345.ingest.us.sentry.io/6789

Optional: Performance monitoring sample rate (0.0-1.0, default: 1.0)

SENTRY_TRACES_SAMPLE_RATE=1.0

Optional: Include personally identifiable information (default: false).

When true, tool inputs and outputs are sent to Sentry.

SENTRY_SEND_DEFAULT_PII=false

Optional: Environment name (e.g., "production", "staging")

SENTRY_ENVIRONMENT=production

Optional: Release version (auto-detected from package if not set)

SENTRY_RELEASE=1.2.3

Optional: Profiling - continuous profiling sample rate (0.0-1.0, default: 1.0)

SENTRY_PROFILE_SESSION_SAMPLE_RATE=1.0

Optional: Profiling - lifecycle mode for profiling (default: "trace")

Options: "all", "continuation", "trace"

SENTRY_PROFILE_LIFECYCLE=trace

Optional: Enable log capture as breadcrumbs and events (default: true)

SENTRY_ENABLE_LOGS=true


#### Features

When enabled, Sentry automatically captures:

- **Exceptions & Errors**: All unhandled exceptions with full context
- **Performance Metrics**: Request/response times and traces
- **MCP Integration**: Detailed MCP server activity and interactions
- **Logs & Breadcrumbs**: Application logs and event trails for debugging
- **Context Data**: Environment, client info, and request parameters

#### Getting a Sentry DSN

1. Create a free account at sentry.io
2. Create a new Python project
3. Copy your DSN from the project settings
4. Set it in your `.env` file

#### Disabling Sentry

Sentry is completely optional. If you don't set `SENTRY_DSN`, the server will run normally without any Sentry integration, and no monitoring data will be collected.

### SSL/TLS Configuration

The server supports SSL certificate verification and custom timeout settings:```env
ZABBIX_VERIFY_SSL=true    # Enable SSL certificate verification
ZABBIX_TIMEOUT=30         # Connection timeout in seconds

Transport Configuration

The server supports multiple transport mechanisms for the MCP protocol:

STDIO Transport (Default)

The default transport uses standard input/output for communication. This is ideal for local usage and integration with tools that communicate via stdin/stdout:```env
MCP_TRANSPORT=stdio


#### HTTP SSE Transport (Server-Sent Events)

For network-based deployments, you can use HTTP with Server-Sent Events. This allows the MCP server to be accessed over HTTP with real-time streaming:```env
MCP_TRANSPORT=sse
MCP_HTTP_HOST=127.0.0.1        # Localhost
MCP_HTTP_PORT=8000           # Port to listen on
MCP_HTTP_BEARER_TOKEN=your-secret-token  # Optional authentication token

When using SSE transport with a bearer token, clients must include the token in their requests:```bash
curl -H "Authorization: Bearer your-secret-token" http://localhost:8000/sse


#### HTTP Streamable Transport

The HTTP Streamable transport provides HTTP-based communication with request/response streaming. This is ideal for web integrations and tools that need HTTP endpoints:```env
MCP_TRANSPORT=http
MCP_HTTP_HOST=127.0.0.1        # Localhost
MCP_HTTP_PORT=8000           # Port to listen on
MCP_HTTP_BEARER_TOKEN=your-secret-token  # Optional authentication token

When using streamable transport with a bearer token:```sh
curl -H "Authorization: Bearer your-secret-token" \
-H "Accept: application/json, text/event-stream" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
http://localhost:8000/mcp


**Note**: The HTTP transport requires proper JSON-RPC formatting with `jsonrpc` and `id` fields. The server may also require session initialization for some operations.

#### Health Endpoint

Both HTTP transports (`sse` and `http`) serve `GET /health`, which answers `200 ok`
when the server is handling requests. It needs no bearer token and does not
contact Zabbix, so a Zabbix outage does not mark the MCP server unhealthy.
The Docker image's `HEALTHCHECK` uses it:```sh
curl http://localhost:8000/health

For more information on FastMCP transports, see the FastMCP documentation.

🤝 Contributing

Contributions are welcome. See CONTRIBUTING.md for the dev setup, checks and commit message format, and use the issue templates for bugs and feature requests.

Found a security problem? Please report it privately as described in SECURITY.md.

📜 License

MIT License - see LICENSE for details.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Zabbix MCP (Mhajder) 怎么安装?

在客户端按下面的安装命令接入:pip install zabbix-mcp。装完在客户端配置里引用同一个包或端点。

Zabbix MCP (Mhajder) 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Zabbix MCP (Mhajder) 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zabbix MCP (Mhajder) 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Zabbix MCP (Mhajder) 能提供哪些能力?

资料显示能力标签包括 协议服务、Python、自动化运维。具体工具清单以官方文档为准。

Zabbix MCP (Mhajder) 需要什么运行环境?

运行时为 Python;属于远程端点,不需要在本地装运行时。

Zabbix MCP (Mhajder) 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为SSE · 服务端推送。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。