Mcp Zabbix

io.github.daedalusPublished by GitHub account daedalusv0.1.0Updated Nov 3, 2026

MCP server for Zabbix API - exposes all Zabbix API functionality via MCP

Overview

AI-generated overview

Local MCP server that exposes Zabbix API methods as tools, letting an assistant query and manage Zabbix monitoring objects.

What you can do
  • Call Zabbix API methods as tools named zabbix_ _ , such as zabbix_host_get or zabbix_host_create
  • Read monitoring configuration and data through the corresponding get methods
  • Create and modify Zabbix objects through the corresponding create and update methods
  • Cover the full Zabbix API surface, since every API method is exposed as a tool
When to use it
Useful when you want an assistant to inspect or administer a Zabbix monitoring instance through its API, for example looking up hosts or creating monitoring objects, without writing API calls by hand.
Requirements
Runs locally as a Python package installed with pip (mcp-zabbix) and started over stdio, either from Python or the mcp-zabbix CLI. Needs a reachable Zabbix API URL in ZABBIX_URL and credentials: an API token in ZABBIX_TOKEN, or a username and password in ZABBIX_USER and ZABBIX_PASSWORD. Network access to the Zabbix server is required.
Before you install
Requires Zabbix API credentials (ZABBIX_TOKEN, or ZABBIX_USER and ZABBIX_PASSWORD) that grant whatever the account allows. Because create and update methods are exposed, the assistant can change monitoring configuration; review write actions before allowing them. Credentials are passed as environment variables, so keep them out of shared configuration files.

Installation

In SourceWeft

  1. Open Mcp Zabbix in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-zabbix

MCP server for Zabbix API - exposes all Zabbix API functionality via MCP

[PyPI] [Python]

mcp-name: io.github.daedalus/mcp-zabbix

Install

bash
pip install mcp-zabbix

Configuration

Set the following environment variables:

  • ZABBIX_URL - Zabbix API URL (required)
  • ZABBIX_TOKEN - API token (required, or use user/password)
  • ZABBIX_USER - Zabbix username (optional)
  • ZABBIX_PASSWORD - Zabbix password (optional)

Usage

python
from mcp_zabbix import mcp
mcp.run()

Or via CLI:

bash
mcp-zabbix

API

The MCP server exposes all Zabbix API methods as tools. Tools follow the pattern:

  • zabbix_<namespace>_<method> (e.g., zabbix_host_get, zabbix_host_create)

Development

bash
git clone https://github.com/daedalus/mcp-zabbix.gitcd mcp-zabbixpip install -e ".[test]"
# run testspytest
# formatruff format src/ tests/
# lintruff check src/ tests/
# type checkmypy src/

Source: README.md at commit f713958

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts