Skip to main content
Glama
zabbix-mcp-server

zabbix-mcp-server

by mpeirone

Zabbix MCP Server

License: GPL v3 Python 3.10+ SafeSkill

A lightweight Model Context Protocol (MCP) server that provides complete access to the entire Zabbix API through just 3 tools. Compatible with Zabbix 6.0+.

Why Zabbix MCP Server?

  • Complete API Coverage - Access every Zabbix API method (100+) through a unified interface

  • Lightweight Context - Only 3 tools instead of 50+ individual tools, keeping LLM context minimal

  • Always Up-to-Date - Works with current and future Zabbix API methods automatically

  • Zabbix 6.0+ Compatible - Supports Zabbix 6.0, 6.4, 7.0, and newer versions

Related MCP server: Zabbix MCP Server

The 3 Tools

Tool

Purpose

zabbix_api

Execute any Zabbix API method

zabbix_api_docs

Get documentation for any API method

zabbix_api_list

Discover available API objects and methods

Quick Start

Option 1: Claude Code Integration

Add to your Claude Code MCP configuration:

claude mcp add zabbix \
  --env ZABBIX_URL=https://your-zabbix-server.com \
  --env ZABBIX_TOKEN=your_api_token \
  -- uvx --from git+https://github.com/mpeirone/zabbix-mcp-server@main zabbix-mcp

Option 2: Run with uv

git clone https://github.com/mpeirone/zabbix-mcp-server.git
cd zabbix-mcp-server
uv sync

# Configure environment
export ZABBIX_URL=https://your-zabbix-server.com
export ZABBIX_TOKEN=your_api_token

# Start the server
uv run python scripts/start_server.py

Test Connection

uv run python scripts/test_server.py

Option 3: Run with docker

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

# Using docker-compose
docker compose up -d

# Or build manually
docker build -t zabbix-mcp-server .
docker run -e ZABBIX_URL=https://zabbix.example.com -e ZABBIX_TOKEN=your_token zabbix-mcp-server

Environment Variables

Required

Variable

Description

Example

ZABBIX_URL

Zabbix server URL

https://your-zabbix-server.com

Authentication (choose one)

Variable

Description

ZABBIX_TOKEN

API token (recommended)

ZABBIX_USER + ZABBIX_PASSWORD

Username and password

Security

Variable

Default

Description

READ_ONLY

false

Set to true to allow only read operations

VERIFY_SSL

true

Enable/disable SSL verification

ZABBIX_API_WHITELIST

.*

Comma-separated regex patterns for allowed API methods

ZABBIX_API_BLACKLIST

(empty)

Comma-separated regex patterns for blocked API methods

ZABBIX_SKIP_VERSION_CHECK

false

Skip Zabbix version compatibility check

ZABBIX_API_TIMEOUT

30

API request timeout in seconds

Transport

Variable

Default

Description

ZABBIX_MCP_TRANSPORT

stdio

Transport type: stdio or streamable-http

ZABBIX_MCP_HOST

127.0.0.1

HTTP server host (when using streamable-http)

ZABBIX_MCP_PORT

8000

HTTP server port (when using streamable-http)

ZABBIX_MCP_STATELESS_HTTP

false

Stateless HTTP mode

AUTH_TYPE

-

Must be no-auth for HTTP transport (when using streamable-http)

Debug

Variable

Default

Description

DEBUG

false

Set to true for verbose logging

Usage Examples

Get Hosts

zabbix_api(method='host.get', params={'output': ['hostid', 'name']})

Get Problems

zabbix_api(method='problem.get', params={'output': 'extend', 'recent': True})

Create Host

zabbix_api(method='host.create', params={
    'host': 'server-01',
    'groups': [{'groupid': '1'}],
    'interfaces': [{'type': 1, 'main': 1, 'useip': 1, 'ip': '192.168.1.100', 'port': '10050'}]
})

Get Method Documentation

zabbix_api_docs(method='host.create')

List Available Methods

zabbix_api_list()              # All objects and methods
zabbix_api_list(object='host')  # Host methods only

Security Features

Read-Only Mode

Set READ_ONLY=true to block all write operations:

export READ_ONLY=true

Only get, version, check, and export operations will be allowed.

API Method Filtering

Control which API methods can be called using whitelist/blacklist patterns:

# Allow only host.* and item.get methods
export ZABBIX_API_WHITELIST="host\..*,item\.get"

# Block all delete and create operations
export ZABBIX_API_BLACKLIST=".*\.delete,.*\.create"

Both support comma-separated regex patterns. Blacklist is checked first.

MCP Client Configuration

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "zabbix": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/mpeirone/zabbix-mcp-server@main", "zabbix-mcp"],
      "env": {
        "ZABBIX_URL": "https://zabbix.example.com",
        "ZABBIX_TOKEN": "your_api_token"
      }
    }
  }
}

Troubleshooting

Connection Issues

  • Verify ZABBIX_URL is accessible

  • Check authentication credentials

  • Ensure Zabbix API is enabled

Permission Errors

  • Verify Zabbix user permissions

  • Check if READ_ONLY mode is enabled

Method Blocked

If you see "Method is not in whitelist" or "Method is blacklisted":

  • Review ZABBIX_API_WHITELIST and ZABBIX_API_BLACKLIST patterns

  • Ensure your regex patterns match the full method name (e.g., host.get)

Debug Mode

export DEBUG=true
uv run python scripts/start_server.py

Contributing

See CONTRIBUTING.md for development guidelines.

License

GPLv3 License - see LICENSE for details.

Acknowledgments

Available Tools

3 tools
zabbix_apiA

Zabbix server: https://zabbix.example.com

Execute Zabbix API method.

This is the main tool for interacting with Zabbix. It requires multiple
iterations to achieve complex goals. Use other tools for guidance.

WORKFLOW:
1. If unsure about method/params: call zabbix_api_docs(method) first
2. If unsure about available methods: call zabbix_api_list() first
3. Execute the API call with this tool
4. If empty results or errors: iterate with different params/filters
5. Continue iterating until goal is achieved

COMMON PATTERNS:
- Finding an object requires 2+ calls (find ID, then get details)
- CPU usage example: Find host by name, get its items, filter CPU item, get history
- Empty results often mean wrong filters - try broader search first

Args:
    method: Zabbix API method (format: 'object.action').
    Examples: 'host.get', 'item.create', 'trigger.update'
    params: Method parameters (optional). For 'get' operations,
    specify 'output' to limit fields (default: ['name']).

Returns:
    JSON response from Zabbix API.

Examples:
# Simple query
zabbix_api('host.get', {'output': ['hostid', 'name']})

# Multi-step: Find host, then get items
# Step 1: Find host ID
hosts = zabbix_api('host.get', {'filter': {'host': 'my-srv-01'}, 'output': ['hostid']})
# Step 2: Get CPU items for that host
items = zabbix_api('item.get', {'hostids': ['12345'], 'search': {'name': 'CPU'}, 'output': ['itemid', 'name']})
# Step 3: Get history for specific item
history = zabbix_api('history.get', {'itemids': ['67890'], 'output': 'extend', 'history': 0, 'limit': 10})

Note:
- Use zabbix_api_docs() for method documentation
- Use zabbix_api_list() for available methods
- Iterate multiple times - complex queries need 2-5 API calls

Inputs: method (required), params. Returns: result

zabbix_api_docsA

Get Zabbix API method documentation.

Call this BEFORE zabbix_api() if you are unsure about method parameters. Shows required/optional parameters with types and descriptions.

Inputs: method (required), version, timeout. Returns: result

zabbix_api_listA

Get available Zabbix API objects and methods.

Call this to discover what API methods are available before using zabbix_api(). Returns all objects and methods discovered dynamically from Zabbix API.

Inputs: object. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct roles: execute API calls, get documentation, and list methods. No overlap in functionality.

    Naming Consistency5/5

    All tools follow the consistent 'zabbix_api_<suffix>' pattern (the main tool is 'zabbix_api' as the base).

    Tool Count4/5

    With 3 tools, the set is minimal but well-scoped for a generic Zabbix API wrapper. Each tool is necessary and sufficient.

    Completeness5/5

    The set covers discovery, documentation, and execution of any Zabbix API method. No gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      A
      maintenance
      Official 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.
      84
      251
      AGPL 3.0
    • A
      license
      C
      quality
      D
      maintenance
      Comprehensive MCP server for integrating with Zabbix monitoring systems, providing 90+ API tools across 19 categories for monitoring, alerting, and infrastructure management.
      100
      15
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes Zabbix monitoring capabilities as callable tools for AI agents and MCP-compatible clients.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that provides Zabbix monitoring data to AI agents, enabling investigation of hosts, metrics, incidents, and triggers with deterministic aggregation.
      -