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
      B
      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
      18 npm
      MIT

    • Monitoring AIops

      AIops-tools
      A
      license
      A
      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

    B3/5.0

    Scored across 110 tools

    Disambiguation3/5

    Many tools target distinct resources and actions, and descriptions often clarify boundaries. However, several closely named tools such as device_ports vs device_ports_get, device_vlans vs switching_vlans, and the various alert/port_group tools can be confused, especially given the sheer number of options.

    Naming Consistency2/5

    Names are all snake_case, but conventions vary: some use plural resource names (devicegroups_list) while related tools use singular (devicegroup_add), verb position shifts between resource_action and resource_subaction, and some tools omit verbs entirely.

    Tool Count1/5

    With 110 tools, the surface is far beyond a well-scoped set. While LibreNMS is broad, this volume creates a sprawling API that is difficult for an agent to navigate and select from reliably.

    Completeness4/5

    Coverage is extensive across devices, ports, alerts, bills, locations, logs, services, health, inventory, routing, and more. Only minor gaps are apparent, such as limited port update fields beyond description or some missing niche lifecycle operations.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources