Zabbix MCP Server

Overview Schema Source Related Servers Discussions Admin

module_get

Read-only

Retrieve registered Zabbix frontend modules, including status, path, and configuration, to inspect custom UI extensions and filter or search them as needed.

Instructions

Retrieve registered frontend modules. Modules extend the Zabbix web interface with custom pages, dashboard widgets, or other UI components. Each module has a status (enabled/disabled) and metadata about its ID, relative path, and configuration.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return.
`filter`	No	Return only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: config (6.4+), id (6.4+), moduleid (6.4+), relative_path (6.4+), status (6.4+). Text properties cannot be filtered; use 'search' for them.
`output`	No	Properties of the module object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: moduleid, relative_path, status. Properties: config (6.4+), id (6.4+), moduleid (6.4+), relative_path (6.4+), status (6.4+).
`search`	No	Return results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: id (6.4+), relative_path (6.4+).
`server`	No	Target Zabbix server. Available: default. Defaults to 'default' if omitted.
`raw_json`	No	Strips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true.
`moduleids`	No	Return only modules with the given IDs.
`sortfield`	No	Sort by one or more of: moduleid, relative_path (comma-separated for several; pair with 'sortorder'). No other property is sortable.
`sortorder`	No	Sort order: 'ASC' (ascending) or 'DESC' (descending).
`countOutput`	No	Return the count of matching results instead of the actual data.
`searchByAny`	No	If true, return results matching ANY search field (OR). Default is ALL fields (AND).
`extra_params`	No	Other native module.get parameters, merged into the request as-is. module.get has no parameters beyond the typed ones. Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call.
`searchWildcardsEnabled`	No	If true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.41.0Oct 20, 2026

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful domain context (module status, ID, relative path, config) but says nothing about pagination, default output shape, or ordering behavior beyond what the schema and annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action and resource, followed by definitional context. Efficient with no filler, though the third sentence about status/metadata is more explanation than operational guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With read-only annotations, full schema description coverage, and an output schema present, the description need not document return values. It supplies enough domain grounding for an agent to know what module_get returns, though it omits permission or pagination context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter carries a detailed description, so the schema does the heavy lifting. The description's mention of status/ID/relative path/config loosely corresponds to filterable and output properties but adds no syntax beyond the schema; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Retrieve') and resource ('registered frontend modules') and then defines what modules are in the Zabbix UI, which lets an agent distinguish this from the many sibling entity-getters. It stops short of naming a sibling tool that could be confused with it, but the resource itself is unique in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use module_get versus alternatives, nor any mention of prerequisites such as needing Super Admin rights for module data. The only implied usage is the verb 'Retrieve', leaving the agent to infer context entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server