← Explore all mcp servers

OBSERVABILITY / initMAX

Zabbix MCP Server

Inspect Zabbix hosts, triggers and alerts and perform selected administration through scoped server tokens.

“Inspect Zabbix hosts, triggers and alerts and perform selected administration through scoped server tokens.”

01 / THE REASONING

Why this made the selection.

  • Inspect Zabbix hosts, triggers and alerts and perform selected administration through scoped server tokens.
  • The setup documentation makes this operating boundary explicit: Zabbix API permissions and per-server/per-token write controls both matter; the admin portal manages users, tokens and server bindings.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md
  • LICENSE
  • pyproject.toml
  • src/zabbix_mcp/config.py

Our findings

  • Zabbix API permissions and per-server/per-token write controls both matter; the admin portal manages users, tokens and server bindings.
  • The user installer still registers a background service. Compact output omits fields unless extended output is requested; report generation is marked Beta.

Not established by this review

  • No server installation, authentication, live tool execution or isolation test was performed.
  • Package/container parity with the pinned source and transitive dependency security were not established.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Review the Linux system or user installer in the pinned checkout; configure the Zabbix URL and API token in config.toml, retain read_only=true, and connect using a generated scoped MCP token or the documented OAuth flow.
  2. Verify the connected account, available tools and target resource before authorizing mutations.

Before you start

  • Pinned package Python requirement: >=3.10.
  • A compatible local process MCP client.
  • Zabbix API permissions and per-server/per-token write controls both matter; the admin portal manages users, tokens and server bindings.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/initMAX/zabbix-mcp-server/blob/1b6e644c2471d5425084d8007ca794769f563dfd/README.md

    Supports: description, setup, capabilities, review, limitations

  2. https://github.com/initMAX/zabbix-mcp-server/blob/1b6e644c2471d5425084d8007ca794769f563dfd/LICENSE

    Supports: license

  3. Pinned package metadata ↗Checked

    https://github.com/initMAX/zabbix-mcp-server/blob/1b6e644c2471d5425084d8007ca794769f563dfd/pyproject.toml

    Supports: install, language, review

  4. https://github.com/initMAX/zabbix-mcp-server/blob/1b6e644c2471d5425084d8007ca794769f563dfd/src/zabbix_mcp/config.py

    Supports: review, install, access, limitations

Evidence & Ask