Skip to main content
Glama
shigechika

io.github.shigechika/aruba-central-mcp

by shigechika

Related Servers

Alternatives to io.github.shigechika/aruba-central-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      An MCP server that exposes WLAN Pi capabilities like device info, Wi-Fi scanning, service management, and VLANs to AI assistants via the wlanpi-core REST API.
      71
      6
      BSD 3-Clause
    • A
      license
      A
      quality
      A
      maintenance
      Low-token MCP server for HPE Networking automation, enabling search of Aruba/HPE docs, OpenAPI details, Central health checks, troubleshooting workflows, configuration management, and guarded ArubaOS 8 migrations and GreenLake Platform operations across platforms like Aruba Central, ClearPass, Mist, and Apstra.
      3
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language management of Aruba ClearPass configuration and API operations through an MCP client, exposing hundreds of ClearPass operations via progressive discovery, OAuth2/API-token authentication, and stdio transport.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A demo MCP server that connects an AI to external systems by exposing Python functions as tools and data as resources, using the stdio transport.
      -

    TDQS

    A3.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct resource/action targets, and several descriptions explicitly cross-reference alternatives such as list_aps vs list_radios. A few pairs still have soft boundaries: list_aps vs get_ap_status, and get_site_summary vs daily_brief.

    Naming Consistency4/5

    Names are consistently snake_case and mostly follow list_/get_/find_ verb_noun patterns. The report-style names health_check, firmware_status, and daily_brief are minor deviations but remain readable and clear.

    Tool Count4/5

    At 18 tools the server is above the typical 3-15 sweet spot, but the broad Aruba Central monitoring domain justifies a fairly wide surface. Most tools cover a distinct resource or analytical view, so the count does not feel bloated.

    Completeness4/5

    The toolset covers core read-only monitoring well: AP/client/switch/WLAN inventory, RF details, throughput and client trends, firmware status, health checks, and site summaries. Minor gaps remain around alerts/events, per-switch port detail, and configuration-changing operations if those are in scope.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive