Skip to main content
Glama

Related Servers

Alternatives to netops-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to drive switches, servers, and consoles over SSH or serial Console through 28 MCP tools, auto-detecting vendors, paging through long output, and cleaning raw byte streams into readable text. Provides structured diagnostics (interfaces, ARP/MAC/routing tables, ping, logs, health checks) plus a three-tier safety model with audit logging, credential redaction, and dry-run config changes.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A governed MCP server that enforces OAuth 2.1 scope checking and policy-driven access control for AI agents, providing a full audit trail on every tool call. It includes tools for Cisco Webex Contact Center knowledge search and SD-WAN network operations.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants and MCP-enabled clients to discover and call application capabilities exposed as structured, schema-defined tools, with input validation, error handling, and API/database integration. It also ships a sample client that demonstrates secure tool execution and seamless AI-agent interoperability.
      -

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool maps to a distinct object/action pair: device inspection, config drafting, log analysis, and ticket create/update. The only mild overlap is between net_inspect_device and net_log_analyze, since both are diagnostic, but their inputs (device ID vs. raw log text) and outputs are clearly separated.

    Naming Consistency3/5

    All names share a net_ prefix, but the structure is mixed: net_inspect_device is verb-first, while net_cfg_draft, net_log_analyze, net_ticket_create and net_ticket_update are noun-first, and 'cfg' is an abbreviation. Readable and grouped, but not a single predictable pattern.

    Tool Count4/5

    Five tools is a compact, well-scoped set where each tool has a distinct role in a plausible network-ops workflow. It is slightly thin (single-device inspection, no batch operations) but not under-served for the stated purpose.

    Completeness3/5

    The surface covers inspect, draft, analyze, and the ticket lifecycle, but has notable gaps: no config apply/push or rollback, no ticket query/list/get beyond creation output, and no device or alert listing. Agents would hit dead ends for read-back and remediation steps.