LibreNMS MCP vs Observability MCP
A side-by-side look at the LibreNMS MCP and Observability 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 Observability 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 Observability MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_sources, list_services, query_metrics.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 44/100 · Fair | 59/100 · Good |
| 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 | None listed |
Tools & capabilities
LibreNMS MCP tools
No tool names declared yet. Check the project README from the listing page.
Observability MCP tools 8
list_sourcesDiscover configured backends and connection statuslist_servicesDiscover monitored services across all backendsquery_metricsQuery metrics with pre-computed summary statsquery_logsQuery logs with error/warning counts and top patternsget_service_healthHealth score combining metrics + logs (0–100)detect_anomaliesCross-signal anomaly detection with robust (median/MAD + trend) analysisget_topologyReturn the merged infrastructure graph (resources + edges) from every topology-capable connector, filterable by source/kind/scopeget_blast_radiusPivot on the universal `RUNS_ON` relation — "if this resource's host fails, who else fails?". Works for pod→node, vm→hypervisor, container→host
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"
}
}
}
}
Observability MCP
{
"mcpServers": {
"observability-mcp": {
"command": "npx",
"args": [
"-y",
"@thotischner/observability-mcp"
]
}
}
}
Frequently asked questions
LibreNMS MCP is categorized under Monitoring and uses a local stdio subprocess. Observability MCP belongs to Monitoring and uses a local stdio subprocess. Pick LibreNMS MCP for monitoring work and Observability 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. Observability 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 observability-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. Observability MCP has 59/100 (Good) with 2 views, 0 installs and 7 GitHub stars.
