Zabbix MCP
MCP server for Zabbix monitoring and automation
Connector by mhajder · GitHub account verified by the MCP Registry
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/mhajder-zabbix-mcp
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: monitoring-observability, incident-response
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.
- Tools
- 24 read · 15 write · 14 delete
- Secrets
- 2 (API keys, tokens or passwords)
- Install scripts
- None found
- Runs as
- Python package
Tools by what they do 53
Read from the source code; the running server may list different tools.
Read 24 · Look things up without changing anything.
action_getapi_versionconfiguration_exportdiscoveryrule_getdrule_getevent_getgraph_gethistory_gethost_gethostgroup_getitem_getitemprototype_get
Show 12 more tools
maintenance_getmediatype_getproblem_getproxy_getscript_getservice_getsla_gettemplate_gettrend_gettrigger_getuser_getusermacro_get
Write 15 · Create, change, send or run things.
host_createhostgroup_createhostgroup_updateitem_createitem_updatemaintenance_createproxy_createproxy_updatetemplate_createtemplate_updatetrigger_createtrigger_update
Show 3 more tools
user_createuser_updateusermacro_create
Delete 14 · Delete, drop, revoke or wipe things.
configuration_importevent_acknowledgehost_deletehost_updatehostgroup_deleteitem_deletemaintenance_deletemaintenance_updateproxy_deletescript_executetemplate_deletetrigger_delete
Show 2 more tools
user_deleteusermacro_delete
Secrets and settings it asks for
Secrets: values you paste in that let it act as you.
ZABBIX_PASSWORDZABBIX_TOKEN
Other settings (environment variables or headers).
DISABLED_TAGSLOG_LEVELRATE_LIMIT_ENABLEDRATE_LIMIT_MAX_REQUESTSRATE_LIMIT_WINDOW_MINUTESREAD_ONLY_MODETOOL_SEARCH_ENABLEDTOOL_SEARCH_MAX_RESULTSTOOL_SEARCH_STRATEGYZABBIX_SKIP_VERSION_CHECKZABBIX_TIMEOUTZABBIX_URL
Show 2 more settings
ZABBIX_USERZABBIX_VERIFY_SSL
Network hosts it talks to 2
github.com· found in codegofastmcp.com· found in code
Tools (53)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
action_getread-onlyGet actions from Zabbix. Actions define automated responses to problems/triggers. They specify what happens when problems occur - sending notifications, executing remote commands, etc. Args: actionids: List of action IDs to get. Omit to return all actions; an empty list matches none. groupids: List of host group IDs to get actions for. An empty list matches none. hostids: List of host IDs to get actions for. An empty list matches none. search: Dictionary with search criteria like {'name': 'notify'}. filter_params: Additional filter parameters for advanced filtering. l…
api_versionread-onlyGet 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. Returns: dict: Contains 'version' key with the API version string (e.g., "6.0.10").
configuration_exportread-onlyExport 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 Args: format_type: Export format. Options:…
configuration_importcan change or delete dataImport configurations into Zabbix. Imports hosts, templates, and other configurations from JSON, XML or YAML. Useful for migration, cloning, or restoring configurations. Args: content: Configuration content to import (JSON, XML or YAML string). format_type: Import format: 'json', 'xml' or 'yaml'. Default is 'json'. rules: Per-object rules controlling what the import may do. Zabbix requires this and applies nothing for object types the rules do not mention, so omitting it silently imports nothing. When not given, a default of createMissing + update…
discoveryrule_getread-onlyGet 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. Args: itemids: List of item IDs (discovery rules are items) to get. An empty list matches none. hostids: List of host IDs to get discovery rules from. An empty list matches none. templateids: List of template IDs to get discovery rules from. An empty list matches none. search: Dictionary with search criteria like {'name': 'SNMP'}. filter_params: Additional filter parameters …
drule_getread-onlyGet 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. Args: druleids: List of network discovery rule IDs to get. Omit to return all rules; an empty list matches none. search: Dictionary with search criteria like {'name': 'LAN'}. filter_params: Additional filter parameters for advanced filtering. limit: Maximum number of results to return (default 100). Set higher for more results. offset: Number of matching record…
event_acknowledgecan change or delete dataAcknowledge 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. Args: eventids: List of event IDs to acknowledge. Find them with event_get. action: Bitmask of operations to apply. Sum the flags to combine them: - 1 = Close the problem (only if the trigger allows manual close) - 2 = Acknowledge the event (default, most common) - 4 = Add message to event - 8 = Change severity - 16 = Unacknowledge the …
event_getread-onlyGet 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. Args: eventids: List of event IDs to get. Omit to return all events; an empty list matches none. groupids: List of host group IDs to get events from. An empty list matches none. hostids: List of host IDs to get events from. An empty list matches none. objectids: List of trigger IDs to get events from. An empty list matches none. …
graph_getread-onlyGet 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. Args: graphids: List of graph IDs to get. Omit to return all graphs; an empty list matches none. hostids: List of host IDs to get graphs from. An empty list matches none. templateids: List of template IDs to get graphs from. An empty list matches none. search: Dictionary with search criteria like {'name': 'CPU'}. filter_params: Additional filter parameters for advanced filtering. …
history_getread-onlyGet 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. Args: itemids: List of item IDs to get history for. Required. Find items with item_get (webitems=True for web scenario items). history: Which history table to read. Zabbix stores each item's values in the table matching its value_type, and reading the wrong one returns an empty list rather than an error - so this must agree with the items. …
host_createCreate 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. Args: host: Technical name of the host (e.g., 'server-prod-01'). Must be unique. groups: List of group IDs to assign this host to. Format: [{'groupid': '10'}]. Every host must belong to at least one group. interfaces: List of host interfaces for data collection. Format: [{'type': 1, 'm…
host_deletecan change or delete dataDelete 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. Args: hostids: List of host IDs to delete. Find them with host_get. Returns: dict: Contains 'hostids' list with deleted host IDs and 'success' flag. Warning: This is permanent. Consider disabling the host instead (set status=1) if you might need to restore it later.
host_getread-onlyGet 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. Args: hostids: Specific host IDs to retrieve. Omit to return all hosts; an empty list matches none. groupids: Filter hosts by group membership (host must belong to these groups). An empty list matches none. templateids: Filter hosts that use specific templates. An empty list matches none. proxyids: Filter hosts assigned …
host_updatecan change or delete dataUpdate 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. Args: hostid: ID of the host to update (required). Find it with host_get. host: New technical name for the host. A blank value is ignored. name: New visible name for display. status: New status: 0=enabled (monitored), 1=disabled (not monitored). description: New description text. templates: The complete ne…
hostgroup_createCreate 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. Args: name: Name of the host group (required). Example: 'Web Servers', 'Database Servers'. Names should be descriptive for organizational clarity. Returns: dict: Contains 'groupids' list with the newly created group ID(s) and 'success' flag. The groupid is needed for other operations like adding hosts to the group. Note: Group names must be unique. Use hostgroup_get to v…
Show 38 more tools
hostgroup_deletecan change or delete dataDelete 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). Args: groupids: List of host group IDs to delete. Find them with hostgroup_get. Returns: dict: Contains 'groupids' list with deleted group IDs and 'success' flag. Warning: If hosts belong to the group, they will no longer be members after deletion. Consider reassigning hosts to different groups before deleting.
hostgroup_getread-onlyGet 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. Args: groupids: List of host group IDs to get. Omit to return all groups; an empty list matches none. Find group IDs with a search or from existing hosts. hostids: Return only groups containing these hosts. An empty list matches none. search: Substring search in group name. Matches partial names like 'Web' finds 'Web Servers'. Case-se…
hostgroup_updateUpdate 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. Args: groupid: ID of the host group to update (required). Find it with hostgroup_get. name: New group name. Returns: dict: Contains 'groupids' list with updated group IDs and 'success' flag.
item_createCreate 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. Args: name: Item name displayed in Zabbix UI. Example: 'CPU load average', 'Memory usage'. key_: Unique item key that identifies the metric. Example: 'system.cpu.load', 'vm.memory.size'. Zabbix agent item keys follow specific naming conventions. hostid: ID of the host this item belongs to. Get from host_get. type_: Collection method: - 0 = Zabbix agent (…
item_deletecan change or delete dataDelete 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. Args: itemids: List of item IDs to delete. Find them with item_get. Returns: dict: Contains 'itemids' list with deleted item IDs and 'success' flag. Warning: Deleting an item removes all its historical data and associated triggers. Consider disabling the item first to test impact before permanent deletion.
item_getread-onlyGet 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. Args: itemids: List of item IDs to get. Omit to return all items; an empty list matches none. hostids: List of host IDs to get items from. Filters items by host. An empty list matches none. groupids: List of group IDs to get items from hosts in those groups. An empty list matches none. templateids: List of template IDs to get items from those templates. An empty list matches none. …
item_updateUpdate 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. Args: itemid: ID of the item to update (required). Find it with item_get. name: New item name. delay: New collection interval (e.g., '30s', '5m', '1h'). units: New units for the values. description: New description. status: New status: 0=enabled (monitored), 1=disabled (not monitored). Returns: dict: Contains 'itemids' list with updated item IDs and 'success' flag.
itemprototype_getread-onlyGet item prototypes from Zabbix. Item prototypes are template items created by discovery rules that generate actual items dynamically based on discovered entities. Args: itemids: List of item prototype IDs to get. An empty list matches none. hostids: List of host IDs to get item prototypes from. An empty list matches none. discoveryids: List of discovery rule IDs to get prototypes from. An empty list matches none. search: Dictionary with search criteria like {'name': 'CPU'}. filter_params: Additional filter parameters for advanced filtering. limit: Maximum number of r…
maintenance_createCreate 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. Args: name: Maintenance name displayed in the UI. Example: 'Server upgrade', 'Network maintenance'. active_since: Start time as Unix timestamp (when maintenance period begins). active_till: End time as Unix timestamp (when maintenance period ends). groupids: List of host group IDs to apply maintenance to. At least one of groupids or hostids is required. ho…
maintenance_deletecan change or delete dataDelete maintenance periods from Zabbix. Cancels maintenance windows immediately, resuming alert generation. If the maintenance period has already passed, historical event suppression is retained. Args: maintenanceids: List of maintenance IDs to delete. Find them with maintenance_get. Returns: dict: Contains 'maintenanceids' list with deleted maintenance IDs and 'success' flag. Note: Alerts will resume immediately upon deletion. If maintenance period has passed, no impact on historical data. Consider timing of deletion to avoid alert storms.
maintenance_getread-onlyGet maintenance periods from Zabbix. Maintenance windows define periods when monitoring is paused for planned upgrades, maintenance, or testing. Alerts are suppressed during maintenance periods. Args: maintenanceids: List of maintenance IDs to get. Omit to return all maintenance periods; an empty list matches none. groupids: List of host group IDs to get maintenance for. An empty list matches none. hostids: List of host IDs to get maintenance for. An empty list matches none. limit: Maximum number of results to return (default 100). Set higher for more results. offset: Num…
maintenance_updatecan change or delete dataUpdate 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. Args: maintenanceid: ID of the maintenance to update (required). Find it with maintenance_get. name: New maintenance name. active_since: New start time (Unix timestamp). active_till: New end time (Unix timestamp). timeperiods: New time periods, replacing all current ones. Same format as maintenance_create. When omitted and the window chan…
mediatype_getread-onlyGet 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. Args: mediatypeids: List of media type IDs to get. Omit to return all media types; an empty list matches none. search: Dictionary with search criteria like {'name': 'Email'}. Zabbix 5.4 renamed the media type 'description' field to 'name'. filter_params: Additional filter parameters for advanced filtering. limit: Maximum number of results to return (default 100). Set high…
problem_getread-onlyGet 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. Args: eventids: List of event IDs to get problems for. Omit to return all problems; an empty list matches none. groupids: List of host group IDs to get problems from. An empty list matches none. hostids: List of host IDs to get problems from. An empty list matches none. objectids: List of trigger IDs to get problems from. An empty list matches none. time_from: Unix timestamp to filt…
proxy_createCreate 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. Args: name: Proxy hostname/identifier. Should match the proxy machine hostname. operating_mode: 0=Active proxy (pulls config from server), 1=Passive proxy (server pushes config). Default is 0 (active). description: Optional description explaining the proxy's purpose or location. Returns: dict: Contains 'proxyids' list with newly created prox…
proxy_deletecan change or delete dataDelete 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. Args: proxyids: List of proxy IDs to delete. Find them with proxy_get. Returns: dict: Contains 'proxyids' list with deleted proxy IDs and 'success' flag. Warning: Hosts using this proxy will lose monitoring until reassigned. Plan reassignment before deleting. Consider if data history should be preserved.
proxy_getread-onlyGet 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. Args: proxyids: List of proxy IDs to get. Omit to return all proxies; an empty list matches none. search: Dictionary with search criteria like {'name': 'proxy1'}. Zabbix 7.0 renamed the proxy 'host' field to 'name' and rejects the old one. filter_params: Additional filter parameters for advanced filtering. limit: Maximum number of results to return (default 100).…
proxy_updateUpdate 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. Args: proxyid: ID of the proxy to update (required). Find it with proxy_get. name: New proxy name/hostname. operating_mode: New operating mode (0=active, 1=passive). description: New description. Returns: dict: Contains 'proxyids' list with updated proxy IDs and 'success' flag.
script_executecan change or delete dataExecute 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. Args: scriptid: ID of the script to execute. Find with script_get. hostid: ID of the host to run the script on. Returns: dict: Contains execution result with status and any output from the script. Returns success flag and response data from the executed script. Warning: Script execution happens remotely on the host. Ensure the script is safe and the host has proper agent/connectivity to e…
script_getread-onlyGet 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. Args: scriptids: List of script IDs to get. Omit to return all scripts; an empty list matches none. hostids: List of host IDs to get scripts for. An empty list matches none. groupids: List of group IDs to get scripts for hosts in those groups. An empty list matches none. search: Dictionary with search criteria like {'name': 'restart'}. filter_params: Additional fi…
service_getread-onlyGet 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. Args: serviceids: List of service IDs to get. Omit to return all services; an empty list matches none. parentids: List of parent service IDs to get child services from. An empty list matches none. search: Dictionary with search criteria like {'name': 'API'}. filter_params: Additional filter parameters for advanced filtering. limit: Maximum number of results to return…
sla_getread-onlyGet 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. Args: slaids: List of SLA IDs to get. Omit to return all SLAs; an empty list matches none. serviceids: List of service IDs to get SLAs for. An empty list matches none. search: Dictionary with search criteria like {'name': 'Website'}. filter_params: Additional filter parameters for advanced filtering. limit: Maximum number of results to return (default 100). Set higher for more results…
template_createCreate 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. Args: name: Template name (required). Example: 'Apache Web Server', 'PostgreSQL Database'. Should describe what the template monitors. description: Optional template description explaining its purpose and use. groups: Template group IDs this template belongs to. Required. Zabbix 6.2 split template groups out from h…
template_deletecan change or delete dataDelete 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. Args: templateids: List of template IDs to delete. Find them with template_get. Returns: dict: Contains 'templateids' list with deleted template IDs and 'success' flag. Warning: Deleting a template removes all associated items, triggers, and graphs from hosts using that template. Consider unlinked the template first if you want to keep the configurations…
template_getread-onlyGet 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. Args: templateids: List of template IDs to get. Omit to return all templates; an empty list matches none. Find template IDs with a search or from host associations. groupids: Return only templates in these template groups. An empty list matches none. hostids: Return only templates linked to these hosts. An empty list matches none. search: Substring search in template …
template_updateUpdate 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. Args: templateid: ID of the template to update (required). Find it with template_get. name: New template name. description: New template description. Returns: dict: Contains 'templateids' list with updated template IDs and 'success' flag.
trend_getread-onlyGet 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. Args: itemids: List of item IDs to get trends for. Required. Find items with item_get (webitems=True for web scenario items). time_from: Unix timestamp to get trends from this time onwards. time_till: Unix timestamp to get trends up to this time. limit: Maximum number of results to return (default 100). Set higher for more res…
trigger_createCreate 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. Args: description: Trigger name displayed in the UI. Example: 'High CPU load', 'Disk space low'. Be descriptive so operators understand what it detects. expression: Trigger expression evaluating item values. Example: 'last(/Zabbix server/system.cpu.load[all,avg1])>0)'. Use Zabbix expression syntax with item references and comparison operators. …
trigger_deletecan change or delete dataDelete 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. Args: triggerids: List of trigger IDs to delete. Find them with trigger_get. Returns: dict: Contains 'triggerids' list with deleted trigger IDs and 'success' flag. Warning: Deleting a trigger stops all alerts and problem detection for that condition. Consider disabling instead (set status=1) if you might need to re-enable it later.
trigger_getread-onlyGet 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. Args: triggerids: List of trigger IDs to get. Omit to return all triggers; an empty list matches none. hostids: List of host IDs to get triggers from. An empty list matches none. groupids: List of group IDs to get triggers from hosts in those groups. An empty list matches none. templateids: List of template IDs to get triggers from those templates. An empty list matches none. …
trigger_updateUpdate 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. Args: triggerid: ID of the trigger to update (required). Find it with trigger_get. description: New trigger name/description. expression: New trigger expression. priority: New severity level (0-5). status: New status: 0=enabled, 1=disabled. comments: New comments/notes. Returns: dict: Contains 'triggerids' list with updated trigger IDs and 'success' flag.
user_createCreate a new user in Zabbix. Creates a new user account with specified credentials, role and group membership. Args: username: Login username. Must be unique and alphanumeric. passwd: Password for the user account. Must meet the instance's password policy, and Zabbix rejects passwords containing the username, name or surname. usrgrps: List of user group assignments in format [{'usrgrpid': 'group_id'}, ...]. Groups control which hosts the user can see. At least one is required. roleid: The role granting the user's permissions. Zabbix accepts user.create…
user_deletecan change or delete dataDelete 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. Args: userids: List of user IDs to delete. Find them with user_get. Returns: dict: Contains 'userids' list with deleted user IDs and 'success' flag. Warning: This action is permanent and immediate. Deleted users lose all access to Zabbix. Consider disabling the user instead (modify type) if temporary removal is needed.
user_getread-onlyGet 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. Args: userids: List of user IDs to get. Omit to return all users; an empty list matches none. search: Dictionary with search criteria like {'username': 'admin'}. Zabbix 5.4 renamed 'alias' to 'username' and rejects the old name. filter_params: Additional filter parameters for advanced filtering. limit: Maximum number of results to return (default 100). Set higher for more results. …
user_updateUpdate 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. Args: userid: ID of the user to update (required). Find it with user_get. username: New username (not recommended - can cause issues). name: New first name. surname: New last name. passwd: New password. roleid: New role for the user. Zabbix 5.2 replaced the numeric user type (1=user, 2=admin, 3=super admin) with role objects, and the default roles keep those ids - 'User …
usermacro_createCreate 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. Args: hostid: ID of the host to create the macro for. Find with host_get. macro: Macro name in format {$NAME}. Must be uppercase alphanumeric with underscores. Example: {$THRESHOLD}, {$API_KEY}. value: Macro value - the actual value substituted when referenced. type_: Macro type: - 0 = Text (plain value) - 1 = Secret (sensitive v…
usermacro_deletecan change or delete dataDelete 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. Args: hostmacroids: List of host macro IDs to delete. Find them with usermacro_get. Returns: dict: Contains 'hostmacroids' list with deleted macro IDs and 'success' flag. Warning: Deleting a macro may break items/triggers that reference it. Verify impact before deletion.
usermacro_getread-onlyGet 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. Args: hostmacroids: List of host macro IDs to get. An empty list matches none. globalmacroids: List of global macro IDs to get. An empty list matches none. hostids: List of host IDs to get macros from. An empty list matches none. templateids: List of template IDs to get macros from. An empty list matches none. globalmacro: If true, return global macros (available to all hosts). searc…
Compare and alternatives
Featured in
Signals
- Stars
- 10
- Forks
- 7
- Open issues
- 0
- Weekly downloads
- 607
- Last commit
- Oct 23, 2026 (5 days ago)
- Last release
- Oct 23, 2026 (5 days ago)
- Last package publish
- Oct 23, 2026 (5 days ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.mhajder/zabbix-mcp- Version
- 0.7.1
- Auth
- API key
- Packages
- pypi zabbix-mcppypi zabbix-mcpoci
ghcr.io/mhajder/zabbix-mcp:0.7.1 - License
- MIT
- Repository
- github.com/mhajder/zabbix-mcp
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
More from mhajder
- 0.665score
LibreNMS MCP
mhajder
MCP server for LibreNMS network monitoring - query devices, ports, alerts, and manage infrastructure
ConnectorAFreshness: ARemoteLocal★ 42↓ 609/wkClaude Code +5 - 0.654score
Ghostfolio MCP
mhajder
MCP server for Ghostfolio portfolio management and financial data access
ConnectorAFreshness: ARemoteLocal★ 22↓ 331/wkClaude Code +5 - 0.630score
NetBox MCP
mhajder
MCP server for NetBox DCIM/IPAM with read-only and dry-run modes
ConnectorAFreshness: ARemoteLocal★ 3↓ 242/wkClaude Code +5 - 0.605score
Oxidized MCP
mhajder
MCP server for Oxidized network device configuration backups
ConnectorAFreshness: ARemoteLocal↓ 230/wkClaude Code +5
Cite this page
Zabbix MCP. Agent Mart. https://agentmart.dev/connectors/mhajder-zabbix-mcp (last updated 2026-10-24)