LibreNMS MCP vs Zabbix MCP
A side-by-side look at the LibreNMS MCP and Zabbix MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose LibreNMS MCP for monitoring work as a local process; choose Zabbix MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose LibreNMS MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
LIBRENMS_URL, LIBRENMS_TOKEN.
Choose Zabbix MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ZABBIX_URL, ZABBIX_TOKEN, ZABBIX_USER, ZABBIX_PASSWORD.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 44/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | LIBRENMS_URLLIBRENMS_TOKEN | ZABBIX_URLZABBIX_TOKENZABBIX_USER |
Tools & capabilities
LibreNMS MCP tools
No tool names declared yet. Check the project README from the listing page.
Zabbix MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
LibreNMS MCP
{
"mcpServers": {
"librenms-mcp": {
"command": "uvx",
"args": [
"librenms-mcp"
],
"env": {
"LIBRENMS_URL": "YOUR_LIBRENMS_URL_HERE",
"LIBRENMS_TOKEN": "YOUR_LIBRENMS_TOKEN_HERE"
}
}
}
}
Zabbix MCP
{
"mcpServers": {
"zabbix-mcp": {
"command": "uvx",
"args": [
"zabbix-mcp"
],
"env": {
"ZABBIX_URL": "YOUR_ZABBIX_URL_HERE",
"ZABBIX_TOKEN": "YOUR_ZABBIX_TOKEN_HERE",
"ZABBIX_USER": "YOUR_ZABBIX_USER_HERE",
"ZABBIX_PASSWORD": "YOUR_ZABBIX_PASSWORD_HERE"
}
}
}
}
Frequently asked questions
LibreNMS MCP is categorized under Monitoring and uses a local stdio subprocess. Zabbix MCP belongs to Monitoring and uses a local stdio subprocess. Pick LibreNMS MCP for monitoring work and Zabbix MCP for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
LibreNMS MCP has no declared pricing — check the project's own site. Zabbix MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add librenms-mcp and zabbix-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, LibreNMS MCP has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 41 GitHub stars. Zabbix MCP has 40/100 (Fair) with 2 views, 0 installs and 10 GitHub stars.
