Skip to main content
Glama
hpe-networking-lab

HPE Networking Assistant

Official
by hpe-networking-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to HPE Networking Assistant

No user-submitted related servers found.

    Related Servers

    • jamf-mcp

      OtakuXavier
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Jamf Pro, Jamf Protect, and Jamf Security Cloud, allowing users to manage devices, security alerts, and configurations through Claude Desktop.
      MIT

    • API-Central

      secure-ssid
      A
      license
      A
      quality
      A
      maintenance
      Enables conversational automation of HPE Aruba Central network operations through Claude Code. Provides 88 tools across monitoring, configuration, and operations domains for device migration, SSID management, switch provisioning, and GreenLake Platform integration.
      16
      2
      MIT

    • Netmiko MCP Server

      Owen123-lang
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Cisco network devices through SSH using Netmiko. Supports retrieving device status, interface details, configurations, and resource monitoring through natural language commands in Claude Desktop.
      -
    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.7/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, from device inventory and client lookup to authentication troubleshooting and config diffing. Even seemingly similar tools like get_clients, get_wired_clients, and get_nac_clients are clearly differentiated by their descriptions (wireless vs. wired vs. Access Assurance). The only mild overlap is between get_access_points and get_offline_access_points, but the latter is a specific filtered view, so confusion is unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern. The verbs vary semantically (generate, get, find, trace, troubleshoot, start, set, export, diff) but are predictable for their function: generate_ for reports, get_ for lists/retrievals, and so on. This consistency allows an agent to infer behavior from the name alone.

    Tool Count3/5

    With 25 tools, the server sits at the upper boundary of the 'heavy' range (16–25). The domain is broad, covering inventory, clients, NAC, Marvis, config management, and session setup, so many tools are justified. However, some report generators (inventory, firmware, health, NAC dashboard) could potentially be consolidated, making the count feel slightly bloated.

    Completeness4/5

    The tool surface provides thorough coverage for network observability, troubleshooting, and configuration backup/compare. It includes inventory, health, client tracking, authentication analysis, Marvis insights, alarms, SLE scores, and port-level details. The main gaps are the lack of write operations (e.g., implementing Marvis fixes) and no singular device detail lookup, but these feel intentional given the assistant's likely read-only role.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources