A comprehensive Model Context Protocol (MCP) server for Zabbix integration using FastMCP and python-zabbix-utils. This server provides complete access to Zabbix API functionality through MCP-compatible tools.

• host_get - Retrieve hosts with advanced filtering
• host_create - Create new hosts with interfaces and templates
• host_update - Update existing host configurations
• host_delete - Remove hosts from monitoring

• hostgroup_get - Retrieve host groups
• hostgroup_create - Create new host groups
• hostgroup_update - Modify existing host groups
• hostgroup_delete - Remove host groups

• item_get - Retrieve monitoring items with filtering
• item_create - Create new monitoring items
• item_update - Update existing items
• item_delete - Remove monitoring items

• trigger_get - Retrieve triggers and alerts
• trigger_create - Create new triggers
• trigger_update - Modify existing triggers
• trigger_delete - Remove triggers

• template_get - Retrieve monitoring templates
• template_create - Create new templates
• template_update - Update existing templates
• template_delete - Remove templates

• problem_get - Retrieve current problems and issues
• event_get - Get historical events
• event_acknowledge - Acknowledge events and problems

• history_get - Access historical monitoring data
• trend_get - Retrieve trend data and statistics

• user_get - Retrieve user accounts
• user_create - Create new users
• user_update - Update user information
• user_delete - Remove user accounts

• proxy_get - Retrieve Zabbix proxies with filtering
• proxy_create - Create new proxies
• proxy_update - Update existing proxies
• proxy_delete - Remove proxies

• maintenance_get - Retrieve maintenance periods
• maintenance_create - Schedule maintenance windows
• maintenance_update - Modify maintenance periods
• maintenance_delete - Remove maintenance schedules

• graph_get - Retrieve graph configurations
• discoveryrule_get - Get discovery rules
• itemprototype_get - Retrieve item prototypes
• configuration_export - Export Zabbix configurations
• configuration_import - Import configurations
• apiinfo_version - Get API version information

• Python 3.10 or higher
• uv package manager
• Access to a Zabbix server with API enabled

1. Clone the repository:

   git clone https://github.com/mpeirone/zabbix-mcp-server.git
   cd zabbix-mcp-server

2. Install dependencies:

   uv sync

3. Configure environment variables:

   cp config/.env.example .env
   # Edit .env with your Zabbix server details

4. Test the installation:

   uv run python scripts/test_server.py

• ZABBIX_URL - Your Zabbix server API endpoint (e.g., https://zabbix.example.com)

Method 1: API Token (Recommended)

• ZABBIX_TOKEN - Your Zabbix API token

Method 2: Username/Password

• ZABBIX_USER - Your Zabbix username
• ZABBIX_PASSWORD - Your Zabbix password

• READ_ONLY - Set to true, 1, or yes to enable read-only mode (only GET operations allowed)
• VERIFY_SSL - Enable/disable SSL certificate verification (default: true)

• ZABBIX_MCP_TRANSPORT - Transport type: stdio (default) or streamable-http

HTTP Transport Configuration (only used when ZABBIX_MCP_TRANSPORT=streamable-http):

• ZABBIX_MCP_HOST - Server host (default: 127.0.0.1)
• ZABBIX_MCP_PORT - Server port (default: 8000)
• ZABBIX_MCP_STATELESS_HTTP - Stateless mode (default: false)
• AUTH_TYPE - Must be set to no-auth for streamable-http transport

With startup script (recommended):

uv run python scripts/start_server.py

Direct execution:

uv run python src/zabbix_mcp_server.py

The server supports two transport methods:

Standard input/output transport for MCP clients like Claude Desktop:

# Set in .env or environment
ZABBIX_MCP_TRANSPORT=stdio

HTTP-based transport for web integrations:

# Set in .env or environment
ZABBIX_MCP_TRANSPORT=streamable-http
ZABBIX_MCP_HOST=127.0.0.1
ZABBIX_MCP_PORT=8000
ZABBIX_MCP_STATELESS_HTTP=false
AUTH_TYPE=no-auth

Note: When using streamable-http transport, AUTH_TYPE must be set to no-auth.

Run test suite:

uv run python scripts/test_server.py

When READ_ONLY=true, the server will only expose GET operations (retrieve data) and block all create, update, and delete operations. This is useful for:

• 📊 Monitoring dashboards
• 🔍 Read-only integrations
• 🔒 Security-conscious environments
• 🛡️ Preventing accidental modifications

Get all hosts:

host_get()

Get hosts in specific group:

host_get(groupids=["1"])

Create a new host:

host_create(
    host="server-01",
    groups=[{"groupid": "1"}],
    interfaces=[{
        "type": 1,
        "main": 1,
        "useip": 1,
        "ip": "192.168.1.100",
        "dns": "",
        "port": "10050"
    }]
)

Get recent problems:

problem_get(recent=True, limit=10)

Get history data:

history_get(
    itemids=["12345"],
    time_from=1640995200,
    limit=100
)

Get all proxies:

proxy_get()

Create a new active proxy:

proxy_create(
    host="proxy-01",
    status=5,
    description="Main datacenter proxy"
)

This server is designed to work with MCP-compatible clients like Claude Desktop. See MCP_SETUP.md for detailed integration instructions.

1. Configure environment:

   cp config/.env.example .env
   # Edit .env with your settings

2. Run with Docker Compose:

   docker compose up -d

docker build -t zabbix-mcp-server .

zabbix-mcp-server/
├── src/
│   └── zabbix_mcp_server.py    # Main server implementation
├── scripts/
│   ├── start_server.py         # Startup script with validation
│   └── test_server.py          # Test script
├── config/
│   ├── .env.example           # Environment configuration template
│   └── mcp.json               # MCP client configuration example
├── pyproject.toml             # Python project configuration
├── requirements.txt           # Dependencies
├── Dockerfile                 # Docker configuration
├── docker-compose.yml         # Docker Compose setup
├── README.md                  # This file
├── MCP_SETUP.md              # MCP integration guide
├── CONTRIBUTING.md           # Contribution guidelines
├── CHANGELOG.md              # Version history
└── LICENSE                   # MIT license

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

# Test server functionality
uv run python scripts/test_server.py

# Test with Docker
docker-compose exec zabbix-mcp python scripts/test_server.py

The server includes comprehensive error handling:

• ✅ Authentication errors are clearly reported
• 🔒 Read-only mode violations are blocked with descriptive messages
• ✔️ Invalid parameters are validated
• 🌐 Network and API errors are properly formatted
• 📝 Detailed logging for troubleshooting

• 🔑 Use API tokens instead of username/password when possible
• 🔒 Enable read-only mode for monitoring-only use cases
• 🛡️ Secure your environment variables
• 🔐 Use HTTPS for Zabbix server connections
• 🔄 Regularly rotate API tokens
• 📁 Store configuration files securely

Connection Failed:

• Verify ZABBIX_URL is correct and accessible
• Check authentication credentials
• Ensure Zabbix API is enabled

Permission Denied:

• Verify user has sufficient Zabbix permissions
• Check if read-only mode is enabled when trying to modify data

Tool Not Found:

• Ensure all dependencies are installed: uv sync
• Verify Python version compatibility (3.10+)

Set environment variable for detailed logging:

export DEBUG=1
uv run python scripts/start_server.py

• FastMCP - MCP server framework
• python-zabbix-utils - Official Zabbix Python library

This project is licensed under the MIT License - see the LICENSE file for details.

• Zabbix for the monitoring platform
• Model Context Protocol for the integration standard
• FastMCP for the server framework

• 📖 Documentation
• 🐛 Issue Tracker
• 💬 Discussions

Made with ❤️ for the Zabbix and MCP communities