Skip to main content
Glama
shigechika

io.github.shigechika/aruba-central-mcp

by shigechika
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

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

No user-submitted related servers found.

    Related Servers

    • wlanpi-mcp

      WLAN-Pi
      A
      license
      Not graded
      quality
      B
      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.
      BSD 3-Clause

    • hpe-networking-mcp

      secure-ssid
      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

    • mcp-intro

      Hugol4ka
      F
      license
      Not graded
      quality
      B
      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.
      -
    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

    A3.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: list_aps versus get_ap_status, list_clients versus find_client_by_mac, and list_radios versus list_bssids are explicit list-vs-detail or list-vs-lookup contrasts. The only mild overlap is get_site_summary and daily_brief, both aggregating site health, but the descriptions differentiate counts from health status.

    Naming Consistency4/5

    The naming pattern is largely consistent: list_* for inventory overviews, get_* for details, trends, and rankings, with find_client_by_mac as a clear lookup exception. health_check and daily_brief break the verb_noun pattern but are easily recognized as operational helpers rather than resource operations.

    Tool Count4/5

    17 tools is slightly above the ideal range but still reasonable for a network-management server covering APs, clients, switches, WLANs, radios, sites, and trends. Each tool maps to a distinct monitoring or troubleshooting need, so the count does not feel padded.

    Completeness4/5

    The server provides strong read-only coverage of the main Aruba Central resources: AP inventory, radio/RF details, client lookup and trends, WLANs, switches, sites, and throughput analytics. Minor gaps exist, such as no switch detail drill-down and no tool to enumerate site IDs for filtering, but agents can usually work around these with existing data.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources