Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to librenms-mcp

No user-submitted related servers found.

    Related Servers

    • Unofficial FortiMonitor MCP

      gjenkins20
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      3
      MIT

    • openwisp-mcp

      marten-lucas
      A
      license
      C
      quality
      B
      maintenance
      MCP server for managing OpenWISP network infrastructure, enabling AI assistants to control devices, templates, topologies, and RADIUS sessions via the OpenWISP REST API.
      92
      14 npm
      MIT

    • Monitoring AIops

      AIops-tools
      A
      license
      B
      quality
      A
      maintenance
      Governs 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.
      42
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 110 tools

    Disambiguation3/5

    Many tools target distinct resources and actions, but the set contains several near-overlapping groups (e.g., ports_search, ports_search_field, ports_search_mac, port_get, device_ports_get; device_fdb, port_fdb, fdb_lookup, ports_search_mac). Descriptions generally clarify boundaries, but the sheer volume makes misselection plausible for less common operations.

    Naming Consistency3/5

    Most names use a resource_action snake_case pattern, but consistency breaks down with singular/plural prefixes (device/devices, devicegroup/devicegroups, alert_template/alert_templates, service/services) and mixed verb styles (list/get/search/create_or_update). Names remain readable but do not follow a single predictable convention.

    Tool Count1/5

    With 110 tools, the surface is extremely large for any single MCP server and far exceeds the recommended 3-15 range. Although LibreNMS is broad, this count creates substantial cognitive load and overlaps that are difficult for an agent to manage reliably.

    Completeness4/5

    Coverage is strong across devices, ports, alerts, bills, groups, locations, services, logs, routing, and switching. Minor gaps exist, such as no delete operation for alert templates and limited create/delete lifecycle for discovered routing entities like BGP sessions, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources