zabbix -nodejs

This Zabbix MCP Server exposes the full Zabbix API surface through the MCP framework, enabling clients to perform monitoring, alerting, and configuration tasks via a standardized MCP protocol. It supports modern authentication using API tokens (recommended) or username/password, and ships with extensive tooling (over 90 tools across 19 categories) for Hosts, Proxies, Items, Triggers, Problems, History, Actions, Templates, Maps, Dashboards, Media, Users, and more. Clients can connect using MCP-compatible clients such as Claude Desktop or Cursor IDE by providing the server name, the Node.js server command, the path to the server script, and the necessary environment variables for authentication. The server emphasizes type-safety, robust validation, and enterprise-grade features like maps, dashboards, SLA monitoring, and error logging.

Prerequisites:

• Node.js 18+ (and npm or yarn)
• Access to a Zabbix server with API access
• Basic familiarity with editing environment variables for your deployment

Install locally:

git clone <repository-url>
cd zabbix-mcp-server
npm install

Configure environment:

# Token-based authentication (recommended)
export ZABBIX_API_URL=https://your-zabbix-server/api_jsonrpc.php
export ZABBIX_API_TOKEN=your_api_token_here

# Or alternative: Username/Password authentication
# export ZABBIX_API_URL=https://your-zabbix-server/api_jsonrpc.php
# export ZABBIX_USERNAME=Admin
# export ZABBIX_PASSWORD=your_password

Run the server:

# Start the MCP server (stdio mode)
npm start

# Or run directly
node src/index.js

# HTTP mode (for development)
MCP_TRANSPORT_MODE=http npm start

If you need to connect to Claude Desktop or Cursor IDE, ensure your MCP configuration JSON points to the correct Node.js entry file and environment variables as shown in the MCP configuration example.

Tips:

• Use the API token authentication mode for production to avoid handling user credentials in logs or config files.
• Ensure ZABBIX_API_URL uses the correct protocol and API endpoint as required by your Zabbix version (5.4+ supports token authentication).
• When deploying, keep API credentials in a secure environment (e.g., secret manager) and avoid committing them to version control.
• If you encounter API version mismatches, verify the Zabbix server version and update the client configuration accordingly.
• For troubleshooting, enable higher log levels in your environment (e.g., LOG_LEVEL=debug) and check the MCP server logs for authentication or connectivity errors.