Zabbix MCP Server
This server lets AI agents query and manage Zabbix monitoring data and configuration through the Model Context Protocol.
Query Zabbix API version and read hosts, host groups, templates, items/item prototypes, triggers, problems, events, history/trends, users, proxies, maintenance periods, actions, media types, graphs, discovery rules, SLAs/services, scripts, and user macros.
Create, update, and delete hosts, host groups, templates, items, triggers, users, proxies, maintenance periods, and host macros.
Acknowledge/close events and execute scripts on monitored hosts.
Export and import Zabbix configurations in JSON, XML, or YAML.
Apply safety controls: read-only mode, tag-based tool filtering, optional tool search, rate limiting, bearer-token auth for HTTP transports, and SSL/timeout settings.
Run over STDIO, SSE, or HTTP Streamable transport, with a
/healthendpoint for HTTP transports.
Optional Sentry integration for error tracking and performance monitoring of the MCP server, configured via SENTRY_DSN and supporting trace sample rates, PII flags, environment/release tagging, session profiling, and log forwarding.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Zabbix MCP Server show my top 10 hosts by CPU usage"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Zabbix MCP Server
Let AI agents query and manage Zabbix monitoring through the Model Context Protocol
Installation ยท Tools ยท Configuration ยท Security
Zabbix MCP Server is a Python-based Model Context Protocol (MCP) server designed to provide advanced, programmable access to Zabbix monitoring data and management features. It exposes a modern API for querying, automating, and integrating Zabbix resources such as hosts, templates, triggers, items, problems, events, users, proxies, maintenance periods, and more. The server supports both read and write operations, robust security features, and is suitable for integration with AI assistants, automation tools, dashboards, and custom monitoring workflows.
โจ Features
Core Features
Query Zabbix hosts, templates, items, triggers, and host groups with flexible filtering
Retrieve problems, events, and alerts with severity filtering
Access history and trend data for monitored items
Monitor trigger states and problem severity
Manage maintenance periods and scheduled downtimes
Retrieve user macros and configuration data
Get SLA and service information
Management Operations
Create, update, and delete hosts, templates, and host groups (if enabled)
Manage triggers, items, and discovery rules
Configure maintenance periods and user macros
Execute scripts on monitored hosts
Acknowledge events and close problems
Create and manage users and proxies
Support for bulk operations on hosts and templates
Advanced Capabilities
Rate limiting and API security features
Read-only mode to restrict all write operations for safe monitoring
Optional tool-search transform for large tool catalogs
Bearer token authentication for HTTP transport
Comprehensive logging and audit trails
SSL/TLS support and configurable timeouts
Multiple transport options (STDIO, SSE, HTTP)
Optional Sentry integration for error tracking
Related MCP server: mcp-zabbix
๐ Installation
Prerequisites
Python 3.11 to 3.15
Access to a Zabbix server. Versions 6.0 to 7.4 are supported - that is the range the
zabbix-utilsclient accepts, and it refuses to connect outside it unlessZABBIX_SKIP_VERSION_CHECK=trueis setValid Zabbix API token or user credentials with appropriate permissions
Quick Install from PyPI
The easiest way to get started is to install from PyPI:
# Using UV (recommended)
uvx zabbix-mcp
# Or using pip
pip install zabbix-mcpRemember to configure the environment variables for your Zabbix instance before running the server:
# Create environment configuration
export ZABBIX_URL=https://zabbix.example.com/api_jsonrpc.php
export ZABBIX_TOKEN=your-zabbix-api-tokenInstall from Source
Clone the repository:
git clone https://github.com/mhajder/zabbix-mcp.git
cd zabbix-mcpInstall dependencies:
# Using UV (recommended)
uv sync
# Or using pip
pip install -e .Configure environment variables:
cp .env.example .env
# Edit .env with your Zabbix URL and credentialsRun the server:
# Using UV (recommended)
uv run zabbix-mcp
# Or using the installed command directly
zabbix-mcpUsing Docker
A Docker image is available on GitHub Packages for easy deployment. It runs the
HTTP Streamable transport on port 8000 (/mcp).
docker pull ghcr.io/mhajder/zabbix-mcp:latestOpen WebUI
Open WebUI 0.6.31 and later connect to the image directly; the separate MCPO
image (ghcr.io/mhajder/zabbix-mcpo) is no longer published. In Open WebUI,
go to Admin Settings > Integrations > External Tool Servers, add a connection
of type MCP (Streamable HTTP) with the URL http://<host>:8000/mcp, and set
Bearer authentication to your MCP_HTTP_BEARER_TOKEN.
Development Setup
For development with additional tools:
# Clone and install with development dependencies
git clone https://github.com/mhajder/zabbix-mcp.git
cd zabbix-mcp
uv sync --group dev
# Run tests
uv run pytest
# Run with coverage
uv run pytest --cov=src/
# Run linting and formatting
uv run ruff check .
uv run ruff format .
# Run type checking
uv run ty check .
# Setup prek hooks
uv run prek install๐ง Configuration
Environment Variables
# Zabbix Connection Details
ZABBIX_URL=https://zabbix.example.com/api_jsonrpc.php
# Authentication - use EITHER token OR user/password
# API Token (preferred over user/password)
ZABBIX_TOKEN=your-api-token
# OR Username/Password (for older versions)
# ZABBIX_USER=Admin
# ZABBIX_PASSWORD=zabbix
# SSL Configuration
ZABBIX_VERIFY_SSL=true
ZABBIX_TIMEOUT=30
ZABBIX_SKIP_VERSION_CHECK=false
# Read-Only Mode
# Set READ_ONLY_MODE true to disable all write operations (create, update, delete)
READ_ONLY_MODE=false
# Disabled Tags
# Comma-separated list of tags to disable tools for (empty by default)
# Example: DISABLED_TAGS=host,user,maintenance
DISABLED_TAGS=
# Logging Configuration
LOG_LEVEL=INFO
# Rate Limiting
# Set RATE_LIMIT_ENABLED true to enable rate limiting
RATE_LIMIT_ENABLED=false
RATE_LIMIT_MAX_REQUESTS=60
RATE_LIMIT_WINDOW_MINUTES=1
# Tool Search Transform (Optional)
# Set TOOL_SEARCH_ENABLED true to replace full tool listing with search tools
TOOL_SEARCH_ENABLED=false
# Search strategy: bm25 (natural language) or regex (pattern matching)
TOOL_SEARCH_STRATEGY=bm25
# Maximum number of matching tools returned by search_tools
TOOL_SEARCH_MAX_RESULTS=5
# Sentry Error Tracking (Optional)
# Set SENTRY_DSN to enable error tracking and performance monitoring
# SENTRY_DSN=https://your-key@o12345.ingest.us.sentry.io/6789
# Optional Sentry configuration
# SENTRY_TRACES_SAMPLE_RATE=1.0
# SENTRY_SEND_DEFAULT_PII=false
# SENTRY_ENVIRONMENT=production
# SENTRY_RELEASE=1.2.3
# SENTRY_PROFILE_SESSION_SAMPLE_RATE=1.0
# SENTRY_PROFILE_LIFECYCLE=trace
# SENTRY_ENABLE_LOGS=true
# MCP Transport Configuration
# Transport type: 'stdio' (default), 'sse' (Server-Sent Events), or 'http' (HTTP Streamable)
# 'streamable-http' is accepted as an alias for 'http'. Any other value stops
# the server at startup.
MCP_TRANSPORT=stdio
# HTTP Transport Settings (used when MCP_TRANSPORT=sse or MCP_TRANSPORT=http)
# Host to bind the HTTP server (default: 127.0.0.1)
# MCP_HTTP_HOST=127.0.0.1
# Port to bind the HTTP server (default: 8000)
# MCP_HTTP_PORT=8000
# Optional bearer token for authentication (leave empty for no auth)
# MCP_HTTP_BEARER_TOKEN=๐งฐ Available Tools
API Information
api_version: Get Zabbix API version information
Host Management
host_get: List hosts with optional filtering by groups, templates, proxies, and search criteriahost_create: Create a new host with interfaces and template linkinghost_update: Update host properties (name, status, description)host_delete: Delete hosts by ID
Host Group Management
hostgroup_get: List host groups with optional filteringhostgroup_create: Create a new host grouphostgroup_update: Update an existing host group's properties (name)hostgroup_delete: Delete host groups
Template Management
template_get: List templates with optional filteringtemplate_create: Create a new templatetemplate_update: Update template properties (name, description)template_delete: Delete templates
Item Management
item_get: List items with optional filtering by hosts, groups, templatesitem_create: Create a new item on a hostitem_update: Update item properties (name, delay, units, description, status)item_delete: Delete items
Trigger Management
trigger_get: List triggers with severity and state filteringtrigger_create: Create a new trigger with expressiontrigger_update: Update trigger properties (description, expression, priority, status, comments)trigger_delete: Delete triggers
Problem & Event Management
problem_get: Get current problems with severity and time filteringevent_get: Get events with time range filteringevent_acknowledge: Acknowledge events with optional messages
History & Trends
history_get: Get historical data for itemstrend_get: Get trend data for items
User Management
user_get: List users with optional filteringuser_create: Create a new useruser_update: Update user properties (username, name, surname, password, role)user_delete: Delete users
Proxy Management
proxy_get: List proxies with optional filteringproxy_create: Create a new proxyproxy_update: Update proxy properties (name, operating mode, description)proxy_delete: Delete proxies
Maintenance Management
maintenance_get: List maintenance periodsmaintenance_create: Create a new maintenance periodmaintenance_update: Update maintenance period properties (name, times, description)maintenance_delete: Delete maintenance periods
Action & Media
action_get: List actions (triggers, autoregistration, etc.)mediatype_get: List media types
Graph & Discovery
graph_get: List graphs with optional filteringdiscoveryrule_get: List LLD discovery rulesdrule_get: List network discovery rulesitemprototype_get: Get item prototypes from discovery rules
SLA & Services
sla_get: List SLAsservice_get: List services
Scripts
script_get: List scriptsscript_execute: Execute a script on a host
User Macros
usermacro_get: List user macros (host and global)usermacro_create: Create a host macrousermacro_delete: Delete host macros
Configuration Management
configuration_export: Export Zabbix configurations to JSON or XMLconfiguration_import: Import Zabbix configurations from JSON or XML
๐ Security & Safety Features
Read-Only Mode
The server supports a read-only mode that disables all write operations for safe monitoring:
READ_ONLY_MODE=trueTag-Based Tool Filtering
You can disable specific categories of tools by setting disabled tags:
DISABLED_TAGS=user,scriptTool Search for Large Toolsets
FastMCP tool search can reduce prompt size for servers with many tools.
When enabled, list_tools returns two synthetic tools:
search_tools: Finds matching tools and returns their full schemascall_tool: Executes any discovered tool by name
Enable it with:
TOOL_SEARCH_ENABLED=true
TOOL_SEARCH_STRATEGY=bm25 # bm25 or regex
TOOL_SEARCH_MAX_RESULTS=8 # optional, default is 5bm25 supports natural language queries, while regex uses a regex
pattern input for deterministic matching.
Tool search respects existing visibility controls (read-only mode and disabled tags).
Rate Limiting
The server supports rate limiting to control API usage and prevent abuse. If enabled, requests are limited per client using a sliding window algorithm.
Enable rate limiting by setting the following environment variables in your .env file:
RATE_LIMIT_ENABLED=true
RATE_LIMIT_MAX_REQUESTS=60 # Maximum requests allowed per window (default: 60)
RATE_LIMIT_WINDOW_MINUTES=1 # Window size in minutesIf RATE_LIMIT_ENABLED is set to true, the server will apply rate limiting middleware. Adjust RATE_LIMIT_MAX_REQUESTS and RATE_LIMIT_WINDOW_MINUTES as needed for your environment.
Sentry Error Tracking & Monitoring (Optional)
The server optionally supports Sentry for error tracking, performance monitoring, and debugging. Sentry integration is completely optional and only initialized if configured.
Installation
To enable Sentry monitoring, install the optional dependency:
# Using UV (recommended)
uv sync --extra sentryConfiguration
Enable Sentry by setting the SENTRY_DSN environment variable in your .env file:
# Required: Sentry DSN for your project
SENTRY_DSN=https://your-key@o12345.ingest.us.sentry.io/6789
# Optional: Performance monitoring sample rate (0.0-1.0, default: 1.0)
SENTRY_TRACES_SAMPLE_RATE=1.0
# Optional: Include personally identifiable information (default: false).
# When true, tool inputs and outputs are sent to Sentry.
SENTRY_SEND_DEFAULT_PII=false
# Optional: Environment name (e.g., "production", "staging")
SENTRY_ENVIRONMENT=production
# Optional: Release version (auto-detected from package if not set)
SENTRY_RELEASE=1.2.3
# Optional: Profiling - continuous profiling sample rate (0.0-1.0, default: 1.0)
SENTRY_PROFILE_SESSION_SAMPLE_RATE=1.0
# Optional: Profiling - lifecycle mode for profiling (default: "trace")
# Options: "manual", "trace"
SENTRY_PROFILE_LIFECYCLE=trace
# Optional: Enable log capture as breadcrumbs and events (default: true)
SENTRY_ENABLE_LOGS=trueFeatures
When enabled, Sentry automatically captures:
Exceptions & Errors: All unhandled exceptions with full context
Performance Metrics: Request/response times and traces
MCP Integration: Detailed MCP server activity and interactions
Logs & Breadcrumbs: Application logs and event trails for debugging
Context Data: Environment, client info, and request parameters
Getting a Sentry DSN
Create a free account at sentry.io
Create a new Python project
Copy your DSN from the project settings
Set it in your
.envfile
Disabling Sentry
Sentry is completely optional. If you don't set SENTRY_DSN, the server will run normally without any Sentry integration, and no monitoring data will be collected.
SSL/TLS Configuration
The server supports SSL certificate verification and custom timeout settings:
ZABBIX_VERIFY_SSL=true # Enable SSL certificate verification
ZABBIX_TIMEOUT=30 # Connection timeout in secondsTransport Configuration
The server supports multiple transport mechanisms for the MCP protocol:
STDIO Transport (Default)
The default transport uses standard input/output for communication. This is ideal for local usage and integration with tools that communicate via stdin/stdout:
MCP_TRANSPORT=stdioHTTP SSE Transport (Server-Sent Events)
For network-based deployments, you can use HTTP with Server-Sent Events. This allows the MCP server to be accessed over HTTP with real-time streaming:
MCP_TRANSPORT=sse
MCP_HTTP_HOST=127.0.0.1 # Localhost
MCP_HTTP_PORT=8000 # Port to listen on
MCP_HTTP_BEARER_TOKEN=your-secret-token # Optional authentication tokenWhen using SSE transport with a bearer token, clients must include the token in their requests:
curl -H "Authorization: Bearer your-secret-token" http://localhost:8000/sseHTTP Streamable Transport
The HTTP Streamable transport provides HTTP-based communication with request/response streaming. This is ideal for web integrations and tools that need HTTP endpoints:
MCP_TRANSPORT=http
MCP_HTTP_HOST=127.0.0.1 # Localhost
MCP_HTTP_PORT=8000 # Port to listen on
MCP_HTTP_BEARER_TOKEN=your-secret-token # Optional authentication tokenWhen using streamable transport with a bearer token:
curl -H "Authorization: Bearer your-secret-token" \
-H "Accept: application/json, text/event-stream" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
http://localhost:8000/mcpNote: The HTTP transport requires proper JSON-RPC formatting with jsonrpc and id fields. The server may also require session initialization for some operations.
Health Endpoint
Both HTTP transports (sse and http) serve GET /health, which answers 200 ok
when the server is handling requests. It needs no bearer token and does not
contact Zabbix, so a Zabbix outage does not mark the MCP server unhealthy.
The Docker image's HEALTHCHECK uses it:
curl http://localhost:8000/healthFor more information on FastMCP transports, see the FastMCP documentation.
๐ค Contributing
Contributions are welcome. See CONTRIBUTING.md for the dev setup, checks and commit message format, and use the issue templates for bugs and feature requests.
Found a security problem? Please report it privately as described in SECURITY.md.
๐ License
MIT License - see LICENSE for details.
Available Tools
53 toolsaction_getAction GetBRead-onlyIdempotent
Get actions from Zabbix.
Actions define automated responses to problems/triggers. They specify what happens when problems occur - sending notifications, executing remote commands, etc.
Inputs: limit, offset, output, search, +7 more. Returns: object
api_versionApi VersionARead-onlyIdempotent
Get Zabbix API version information.
This tool retrieves the current version of the Zabbix API you are connecting to. This is useful for understanding API capabilities and ensuring compatibility with specific features that may be version-dependent.
Inputs: no named parameters. Returns: object
configuration_exportConfiguration ExportARead-onlyIdempotent
Export Zabbix configurations.
Exports monitored hosts, templates, and their complete configurations to JSON, XML, or YAML format. Useful for backup, migration, disaster recovery, or sharing configurations.
When you export templates or hosts, the export includes:
All associated items (metrics/data sources)
All triggers and their dependencies
Discovery rules and prototypes
Graphs and visualizations
Macros and variable definitions
Host groups and interfaces (for hosts)
Inventory data (for hosts)
And all other configuration elements
Inputs: hostids, format_type, prettyprint, templateids. Returns: object
configuration_importConfiguration ImportBDestructive
Import configurations into Zabbix.
Imports hosts, templates, and other configurations from JSON, XML or YAML. Useful for migration, cloning, or restoring configurations.
Inputs: content (required), rules, format_type, delete_missing. Returns: object
discoveryrule_getDiscoveryrule GetBRead-onlyIdempotent
Get discovery rules from Zabbix.
Discovery rules automatically detect items, triggers, and interfaces from network resources. They enable dynamic host and item management without manual configuration.
Inputs: limit, offset, output, search, +7 more. Returns: object
drule_getDrule GetBRead-onlyIdempotent
Get network discovery rules from Zabbix.
Network discovery (drule) rules perform network scanning to discover hosts and services. They can scan for active devices, open ports, and available services in CIDR ranges.
Inputs: limit, offset, output, search, +5 more. Returns: object
event_acknowledgeEvent AcknowledgeADestructiveIdempotent
Acknowledge events in Zabbix.
Mark events (problems/alerts) as acknowledged to show that operations staff are aware of and working on the issue. Acknowledged events can also be closed if resolved.
Inputs: eventids (required), action, message. Returns: object
event_getEvent GetARead-onlyIdempotent
Get events from Zabbix.
Events represent state changes in the system - when triggers transition from normal to problem and back, or recovery events. Each event has a timestamp, trigger, and can be acknowledged to show operators have seen the alert.
Inputs: limit, offset, output, hostids, +13 more. Returns: object
graph_getGraph GetCRead-onlyIdempotent
Get graphs from Zabbix.
Graphs visualize item data over time, displaying metric values in line/bar/pie charts. Graphs can be included in dashboards, reports, and custom views for data analysis.
Inputs: limit, offset, output, search, +10 more. Returns: object
history_getHistory GetARead-onlyIdempotent
Get history data from Zabbix.
Retrieves the raw metric values collected by items. History contains all individual collected data points with timestamps, allowing detailed analysis of system behavior over time.
Inputs: itemids (required), limit, history, sortfield, +4 more. Returns: object
host_createHost CreateA
Create a new host in Zabbix.
Adds a new monitored host to Zabbix. This is essential for starting to monitor a new server or device. You must specify at least a host name and groups. You can optionally configure interfaces (for agent/SNMP communication) and link templates.
Inputs: host, name, groups, params, +4 more. Returns: object
host_deleteHost DeleteADestructive
Delete hosts from Zabbix.
Permanently removes one or more hosts from Zabbix. This will delete all associated data including history and alerts. Use with caution as this is a destructive operation.
Inputs: hostids (required). Returns: object
host_getHost GetARead-onlyIdempotent
Get hosts from Zabbix with optional filtering.
Retrieves a list of monitored hosts from Zabbix. You can filter by host IDs, groups, templates, proxies, or use search criteria. This is useful for discovering which hosts are available in your monitoring system.
Inputs: limit, offset, output, search, +14 more. Returns: object
hostgroup_createHostgroup CreateB
Create a new host group in Zabbix.
Host groups serve as containers for organizing hosts. They're essential for applying permissions, templates, and maintenance windows to multiple hosts at once.
Inputs: name (required). Returns: object
hostgroup_deleteHostgroup DeleteADestructive
Delete host groups from Zabbix.
Permanently removes one or more host groups. Hosts in deleted groups will no longer be members of that group (though the hosts themselves remain unless explicitly deleted).
Inputs: groupids (required). Returns: object
hostgroup_getHostgroup GetBRead-onlyIdempotent
Get host groups from Zabbix.
Retrieves host groups with optional filtering. Host groups are used to organize and manage hosts collectively, applying templates, permissions, and maintenance windows to multiple hosts at once.
Inputs: limit, offset, output, search, +7 more. Returns: object
hostgroup_updateHostgroup UpdateA
Update an existing host group in Zabbix.
Modifies properties of an existing host group. You can change the group's name. Only specify the fields you want to change.
Inputs: groupid (required), name. Returns: object
host_updateHost UpdateADestructiveIdempotent
Update an existing host in Zabbix.
Modifies properties of an existing host. You can change the technical name, visible name, status (enable/disable monitoring), description, linked templates, or the proxy that monitors it. Only specify the fields you want to change.
Inputs: hostid (required), host, name, status, +4 more. Returns: object
item_createItem CreateB
Create a new item in Zabbix.
Items define what data is collected from a host. Each item specifies the metric name, how to collect it (agent, SNMP, etc.), what interval to use, and what data type to store.
Inputs: key_ (required), name (required), type_ (required), hostid (required), +5 more. Returns: object
item_deleteItem DeleteADestructive
Delete items from Zabbix.
Permanently removes one or more items from monitoring. The item's historical data is typically removed as part of cleanup, though this depends on Zabbix configuration.
Inputs: itemids (required). Returns: object
item_getItem GetBRead-onlyIdempotent
Get items (metrics) from Zabbix.
Items are the data sources in Zabbix - they define what metrics are collected and how (protocol, interval, etc.). Each item produces a stream of values over time.
Inputs: limit, offset, output, search, +14 more. Returns: object
itemprototype_getItemprototype GetBRead-onlyIdempotent
Get item prototypes from Zabbix.
Item prototypes are template items created by discovery rules that generate actual items dynamically based on discovered entities.
Inputs: limit, offset, output, search, +7 more. Returns: object
item_updateItem UpdateA
Update an existing item in Zabbix.
Modifies properties of an existing monitoring item. You can change the name, collection interval, units, or status. Only specify the fields you want to change.
Inputs: itemid (required), name, delay, units, +2 more. Returns: object
maintenance_createMaintenance CreateA
Create a new maintenance period in Zabbix.
Schedules a maintenance window when monitoring alerts are suppressed. Useful for planned upgrades, patching, or system maintenance without triggering false alarms.
Inputs: name (required), active_till (required), active_since (required), hostids, +3 more. Returns: object
maintenance_deleteMaintenance DeleteADestructive
Delete maintenance periods from Zabbix.
Cancels maintenance windows immediately, resuming alert generation. If the maintenance period has already passed, historical event suppression is retained.
Inputs: maintenanceids (required). Returns: object
maintenance_getMaintenance GetBRead-onlyIdempotent
Get maintenance periods from Zabbix.
Maintenance windows define periods when monitoring is paused for planned upgrades, maintenance, or testing. Alerts are suppressed during maintenance periods.
Inputs: limit, offset, output, hostids, +5 more. Returns: object
maintenance_updateMaintenance UpdateBDestructive
Update an existing maintenance period in Zabbix.
Modifies properties of an existing maintenance window. You can change the name, start time, end time, time periods, or description. Only specify the fields you want to change.
Inputs: maintenanceid (required), name, active_till, description, +2 more. Returns: object
mediatype_getMediatype GetBRead-onlyIdempotent
Get media types from Zabbix.
Media types define communication channels for sending notifications (email, SMS, webhooks, etc.). Actions use media types to deliver alerts to users and integrations.
Inputs: limit, offset, output, search, +5 more. Returns: object
problem_getProblem GetBRead-onlyIdempotent
Get problems from Zabbix.
Problems are active trigger states that indicate issues with monitored infrastructure. Each problem is associated with a trigger and can be acknowledged by operators.
Inputs: limit, offset, output, recent, +15 more. Returns: object
proxy_createProxy CreateA
Create a new proxy in Zabbix.
Proxies allow distributed monitoring by collecting data from remote networks and reporting to the central Zabbix server. Useful for firewall-separated networks or high-latency connections.
Inputs: name (required), description, operating_mode. Returns: object
proxy_deleteProxy DeleteADestructive
Delete proxies from Zabbix.
Permanently removes proxy definitions. Hosts assigned to deleted proxies will need to be reassigned to other proxies or the server. Data from deleted proxies is typically retained.
Inputs: proxyids (required). Returns: object
proxy_getProxy GetCRead-onlyIdempotent
Get proxies from Zabbix.
Proxies act as data collection points for Zabbix, allowing monitoring of remote networks without direct connectivity. Proxies collect data locally and report to the Zabbix server.
Inputs: limit, offset, output, search, +5 more. Returns: object
proxy_updateProxy UpdateA
Update an existing proxy in Zabbix.
Modifies properties of an existing proxy. You can change the name, operating mode, or description. Only specify the fields you want to change.
Inputs: proxyid (required), name, description, operating_mode. Returns: object
script_executeScript ExecuteBDestructive
Execute a script on a host in Zabbix.
Runs a custom script on a specified host. Used for executing remediation tasks, configuration changes, or diagnostic commands remotely.
Inputs: hostid (required), scriptid (required). Returns: object
script_getScript GetBRead-onlyIdempotent
Get scripts from Zabbix.
Scripts are custom automation routines that can be executed on monitored hosts or the server. They can be triggered manually or by actions to automate remediation or configuration tasks.
Inputs: limit, offset, output, search, +7 more. Returns: object
service_getService GetBRead-onlyIdempotent
Get services from Zabbix.
Services represent business capabilities or applications (e.g., 'Web Application', 'Database'). Services can depend on other services, creating hierarchies for tracking dependencies.
Inputs: limit, offset, output, search, +6 more. Returns: object
sla_getSla GetCRead-onlyIdempotent
Get SLAs from Zabbix.
Service Level Agreements (SLAs) define uptime and availability targets for services. They track compliance with service objectives and generate reports on availability.
Inputs: limit, offset, output, search, +6 more. Returns: object
template_createTemplate CreateB
Create a new template in Zabbix.
Templates define the monitoring configuration (items, triggers, graphs) that can be reused across multiple hosts. Creating custom templates enables standardized monitoring for specific applications or server types.
Inputs: host (required), groups (required), name, description. Returns: object
template_deleteTemplate DeleteADestructive
Delete templates from Zabbix.
Permanently removes one or more templates. Hosts that have the deleted templates applied will lose those template's items, triggers, and graphs. The hosts themselves remain unchanged.
Inputs: templateids (required). Returns: object
template_getTemplate GetBRead-onlyIdempotent
Get templates from Zabbix.
Templates are reusable collections of items, triggers, and graphs that can be applied to hosts. They standardize monitoring across multiple servers with the same role.
Inputs: limit, offset, output, search, +12 more. Returns: object
template_updateTemplate UpdateA
Update an existing template in Zabbix.
Modifies properties of an existing template. You can change the name or description. Only specify the fields you want to change.
Inputs: templateid (required), name, description. Returns: object
trend_getTrend GetARead-onlyIdempotent
Get trend data from Zabbix.
Trends are aggregated (summarized) historical data providing min/max/average values at hour-long intervals. Trends use less storage than raw history while preserving statistical information for long-term analysis.
Inputs: itemids (required), limit, time_from, time_till, +1 more. Returns: object
trigger_createTrigger CreateC
Create a new trigger in Zabbix.
Triggers define the conditions under which problems are detected. They use expressions to evaluate item values and determine when to transition from normal to problem state.
Inputs: expression (required), description (required), status, comments, +1 more. Returns: object
trigger_deleteTrigger DeleteADestructive
Delete triggers from Zabbix.
Permanently removes one or more triggers. Hosts will no longer generate alerts for these conditions. Historical trigger data and associated problems are typically retained.
Inputs: triggerids (required). Returns: object
trigger_getTrigger GetCRead-onlyIdempotent
Get triggers from Zabbix.
Triggers are rules that define when a problem occurs based on item values. They evaluate expressions against collected metrics and transition between problem and normal states.
Inputs: limit, offset, output, search, +12 more. Returns: object
trigger_updateTrigger UpdateA
Update an existing trigger in Zabbix.
Modifies properties of an existing trigger. You can change the description, expression, priority, status, or comments. Only specify fields you want to change.
Inputs: triggerid (required), status, comments, priority, +2 more. Returns: object
user_createUser CreateB
Create a new user in Zabbix.
Creates a new user account with specified credentials, role and group membership.
Inputs: passwd (required), usrgrps (required), username (required), name, +2 more. Returns: object
user_deleteUser DeleteADestructive
Delete users from Zabbix.
Permanently removes user accounts from the system. The user's access will be immediately revoked. Historical data and previous actions by the user are retained for audit purposes.
Inputs: userids (required). Returns: object
user_getUser GetBRead-onlyIdempotent
Get users from Zabbix.
Users represent people with access to the Zabbix system. Each user has authentication credentials and permission level determining what they can view and modify.
Inputs: limit, offset, output, search, +5 more. Returns: object
usermacro_createUsermacro CreateB
Create a new host macro in Zabbix.
Host macros define custom variables for specific hosts. They can be referenced in items and triggers using {$MACRO_NAME} syntax, allowing dynamic configuration without editing items.
Inputs: macro (required), value (required), hostid (required), type_, +1 more. Returns: object
usermacro_deleteUsermacro DeleteADestructive
Delete host macros from Zabbix.
Permanently removes host-level macro definitions. Items and triggers using this macro will no longer be able to reference it, potentially causing parsing errors.
Inputs: hostmacroids (required). Returns: object
usermacro_getUsermacro GetCRead-onlyIdempotent
Get user macros from Zabbix.
User macros are variables that can be referenced in items, triggers, and scripts. They allow parameterization of monitoring configurations with custom values.
Inputs: limit, offset, output, search, +9 more. Returns: object
user_updateUser UpdateB
Update an existing user in Zabbix.
Modifies properties of an existing user account. You can change name, surname, password, or role. Only specify the fields you want to change.
Inputs: userid (required), name, passwd, roleid, +2 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 53 tools
Most tools map to a distinct resource and action, making core selection straightforward. The main ambiguous pairs are problem_get vs event_get and discoveryrule_get vs drule_get, where descriptions are needed to clarify the boundary.
The dominant pattern is predictable snake_case resource_action naming, such as host_get, host_create, and trigger_update. Minor deviations include api_version lacking an action verb, drule_get abbreviating discoveryrule_get, and compact compounds like hostgroup and usermacro.
With 53 tools, the server is far above the well-scoped 3-15 range and places a heavy burden on tool selection. The broad Zabbix domain justifies many operations, but the set still feels unwieldy and includes many separate read-only getters.
Core monitoring objects such as hosts, host groups, items, triggers, templates, maintenance, users, and proxies have CRUD coverage, and history/trends/events are readable. However services, SLAs, actions, media types, graphs, discovery rules, and scripts are largely read-only or missing create/update/delete, leaving notable lifecycle gaps.
Maintenance
Related MCP Connectors
Uptime, cron/heartbeat, TLS and domain expiry monitoring, EU-hosted. Same access as the REST API.
Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
Scopable MSP API: clients, quotes, assessments, compliance, QBRs. OAuth 2.1, read-only or read-write
Manage ZAP-Hosting game servers, VPS, dedicated servers, TeamSpeak and domains from your AI client.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables users to monitor and query Zabbix infrastructure through natural language by providing access to current problems, active triggers, and system health status via the Zabbix API.-
- AlicenseCqualityDmaintenanceExposes the complete Zabbix API functionality through the Model Context Protocol, mapping API methods to tools for managing hosts, triggers, and monitoring data. It enables seamless integration and control of Zabbix monitoring environments via natural language interfaces.10024 PyPIMIT
- AlicenseBqualityAmaintenanceOfficial 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.84251AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceExposes Zabbix monitoring capabilities as callable tools for AI agents and MCP-compatible clients.-