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
      Not graded
      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.
      26
      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
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3/5.0

    Scored across 110 tools

    Disambiguation2/5

    Many tool clusters are easy to confuse: device_ports vs device_ports_get vs port_get, alerts_get vs alert_get_by_id vs alert_rule_get, port_fdb vs device_fdb vs fdb_lookup, and ports_search vs ports_search_field vs ports_search_mac all require careful reading to avoid misselection. The descriptions help, but at this scale the boundaries between similar tools are genuinely unclear.

    Naming Consistency3/5

    Most names use snake_case with resource prefixes and readable verb placement, but conventions are mixed: plural list names like devicegroups_list collide with singular action names like devicegroup_add, and some tools are noun phrases like system_info or health_by_type. Overall it is fairly navigable but not pattern-predictable.

    Tool Count1/5

    110 tools is an extreme number for a single MCP server, far beyond the typical well-scoped range and even beyond the 50+ extreme threshold. Even for a broad platform like LibreNMS, this creates a large selection burden and should be split into smaller domain-focused servers.

    Completeness4/5

    The surface is impressively broad, covering device lifecycle, alerts, alert rules/templates, bills, locations, ports, services, logs, and many network data views. Minor gaps exist such as no alert template delete, no port group deletion/update, and no explicit maintenance-clear tool, but these are workable rather than blocking.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources