Skip to main content
Glama

Related Servers

Alternatives to cnc-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables AI-powered network automation through natural language interactions with Cisco NSO, providing access to device management, configuration retrieval, sync operations, and service orchestration via the RESTCONF API.
      9
      4
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables an AI assistant to search, inspect and run vendor API operations for HPE Aruba Networking Central, Juniper Mist and HPE Aruba Networking ClearPass through four tools covering tool discovery, read-only execution, full invocation with change classification, and per-product login checks. Writes and disruptive actions are refused or flagged, so network changes only happen with explicit approval.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to directly inspect, configure, test, and orchestrate network devices through pyATS/Genie, including show command parsing, config rollback, feature state learning/diffing, fleet-wide command fan-out, and declarative test execution.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable AI agents to observe, troubleshoot, and configure Aruba CX (AOS-CX) switches through REST and SSH, with safety controls, inventory management, and verification workflows.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with the Netdisco network management platform through its complete REST API, supporting device inspection, port queries, VLAN searches, and job management.
      MIT

    TDQS

    A4.3/5.0

    Scored across 19 tools

    Disambiguation4/5

    Each tool targets a distinct resource and action, and descriptions explicitly partition the topology tools (cnc_get_topology for adjacency vs cnc_list_topology_nodes/cnc_list_topology_links for tabular attributes). The only mild overlap is between the general topology getter and the two specialized topology listers, but the descriptions give clear guidance on when to use each.

    Naming Consistency5/5

    Every tool follows the same cnc_<verb>_<noun> convention (list_*, get_*, wait_for_*), with no camelCase or mixed-style deviations. The pattern is fully predictable across all 19 tools.

    Tool Count4/5

    19 tools is on the heavier side but each covers a genuinely distinct domain (devices, credentials, providers, topology, tags, users, applications, alarms, jobs) with read variants plus helpful summary/wait helpers. It feels slightly large but well-scoped rather than padded.

    Completeness4/5

    Read coverage is broad and coherent: devices, credentials, providers, topology, tags, users, applications, alarms and inventory jobs all have list/get surfaces, plus convergence-wait helpers. The notable gap is the complete absence of write operations (create/update/delete) even though descriptions reference them, but the surface appears intentionally read-only.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues