Zabbix MCP

Prerequisites

• Python 3.11 to 3.14
• Access to a Zabbix server (5.4+)
• Valid Zabbix API token or user credentials with appropriate permissions

Clone and install with development dependencies

git clone https://github.com/mhajder/zabbix-mcp.git cd zabbix-mcp uv sync --group dev

Installation

Quick Install from PyPI

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

```sh

Install from Source

1. Clone the repository:

git clone https://github.com/mhajder/zabbix-mcp.git
cd zabbix-mcp

1. Install dependencies:

```sh

Or using the installed script

zabbix-mcp ```

Using Docker

Docker images are available on GitHub Packages for easy deployment.

```sh

Development Setup

For development with additional tools:

```sh

Setup prek hooks

uv run prek install ```

MCPO image for usage with Open WebUI

docker pull ghcr.io/mhajder/zabbix-mcpo:latest ```

Example: DISABLED_TAGS=host,user,maintenance

DISABLED_TAGS=

SENTRY_TRACES_SAMPLE_RATE=1.0

SENTRY_PROFILE_SESSION_SAMPLE_RATE=1.0

Create environment configuration

export ZABBIX_URL=https://zabbix.example.com/api_jsonrpc.php export ZABBIX_TOKEN=your-zabbix-api-token ```

Edit .env with your Zabbix URL and credentials

4. Run the server:

Configuration

Environment Variables

```env

SSL Configuration

ZABBIX_VERIFY_SSL=true ZABBIX_TIMEOUT=30 ZABBIX_SKIP_VERSION_CHECK=false

Logging Configuration

LOG_LEVEL=INFO

Tool Search Transform (Optional)

Sentry Error Tracking (Optional)

Optional Sentry configuration

SENTRY_ENVIRONMENT=production

MCP Transport Configuration

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

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

MCP_HTTP_BEARER_TOKEN= ```

Configuration Management

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

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

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

SENTRY_TRACES_SAMPLE_RATE=1.0

Optional: Include personally identifiable information (default: true)

SENTRY_SEND_DEFAULT_PII=true

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:

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:

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:

MCP_TRANSPORT=sse
MCP_HTTP_HOST=0.0.0.0        # Bind to all interfaces (or specific IP)
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:

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:

MCP_TRANSPORT=http
MCP_HTTP_HOST=0.0.0.0        # Bind to all interfaces (or specific IP)
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:

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.

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

API Token (preferred for Zabbix 5.4+)

ZABBIX_TOKEN=your-api-token

Host to bind the HTTP server (default: 0.0.0.0 for all interfaces)

MCP_HTTP_HOST=0.0.0.0

API Information

• api_version: Get Zabbix API version information