mcp-zabbix
MCP server for Zabbix API - exposes all Zabbix API functionality via MCP
mcp-name: io.github.daedalus/mcp-zabbix
Install
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
from mcp_zabbix import mcp
mcp.run()
Or via CLI:
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
git clone https://github.com/daedalus/mcp-zabbix.git
cd mcp-zabbix
pip install -e ".[test]"
# run tests
pytest
# format
ruff format src/ tests/
# lint
ruff check src/ tests/
# type check
mypy src/
Metadata
Release files for mcp-zabbix 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_zabbix-0.1.0.tar.gz | 4.8 kB | With provenance | Details for mcp_zabbix-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_zabbix-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for mcp_zabbix-0.1.0-py3-none-any.whl |
Total release size: 11.0 kB
Release files / mcp_zabbix-0.1.0.tar.gz
| Download URL | mcp_zabbix-0.1.0.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9deb1233e9eef83e2b2d1b650536ebe71393fc48d09135986e93642dd0aaf6ea
|
|
BLAKE2b-256 checksum How to use checksums |
6f16616d78bd92e63aecaf84ecba86cfff9525e0fde8c1edcbee1a90c2cf55f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 29, 2026.
Transparency logRelease files / mcp_zabbix-0.1.0-py3-none-any.whl
| Download URL | mcp_zabbix-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5deed77d624500983e3102600cbddb74782d55c0c754b66a52975fba9b3b77c8
|
|
BLAKE2b-256 checksum How to use checksums |
e594c8c86ca199d17ff1cd47f1996a4c7e3dc57b90e0901b15201ea34804dc33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 29, 2026.
Transparency logSecurity for mcp-zabbix 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for mcp_zabbix-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.