librenms-mcp
Related Servers
Alternatives to librenms-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for LibreNMS network monitoring — query devices, alerts, sensors, ports, and more through AI assistants like Claude.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the FortiMonitor v2 monitoring API. 241 tools across 33 modules covering server management, outage monitoring, maintenance windows, metrics, notifications, cloud monitoring, SNMP, dashboards, reporting, and more. Unofficial community project, not affiliated with Fortinet. Python, MIT license, Docker and local deployment supported.3MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with NetBox API, enabling users to query and manage NetBox resources such as devices through natural language.MIT
- AlicenseCqualityBmaintenanceA Python-based MCP server that enables querying Cisco's Meraki Dashboard API to discover, monitor, and manage Meraki environments.2247MIT
- FlicenseCqualityCmaintenanceMCP server for managing OpenWISP network infrastructure, enabling AI assistants to control devices, templates, topologies, and RADIUS sessions via the OpenWISP REST API.92-
- AlicenseAqualityBmaintenanceGoverns and automates network monitoring across SolarWinds Orion and Paessler PRTG platforms with a unified MCP server, enabling querying, alert management, and governed writes with audit logging.42MIT
TDQS
Scored across 113 tools
Many tools are distinct, but several overlap: fdb_lookup and ports_search_mac both find ports by MAC, while device_ports, device_ports_get, port_get, ports_list, and ports_search are near-neighbors. Descriptions often clarify boundaries, but the set still requires careful selection among similar lookup/list tools.
The surface is mostly snake_case, but conventions are mixed: noun-first names like logs_eventlog and health_list coexist with verb-first names like alert_rule_add. Singular/plural inconsistency (devicegroup vs devicegroups, port_group_add vs port_groups_list) makes the pattern only partly predictable.
113 tools is far beyond a practical surface for reliable agent selection, even for a broad network-monitoring domain. Many tools are granular list/search/get variants, making this an extreme count mismatch.
Core LibreNMS domains are extensively covered: devices, ports, alerts/rules/templates, billing, health/sensors, logs, groups, locations, routing, switching, NAC, Oxidized, and services. Minor lifecycle gaps remain, such as no alert_template_delete and limited port create/delete or maintenance variants, but most workflows are supported.