Skip to main content
Glama
fmcglinn

peering-manager-mcp-server

by fmcglinn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to peering-manager-mcp-server

No user-submitted related servers found.

    Related Servers

    • NetBox MCP Server by netboxlabs

      NetBox MCP Serverofficial

      netboxlabs
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for NetBox that enables LLMs to query NetBox objects (devices, IPAM, etc.) and change logs through natural language, with field filtering for token optimization.
      4
      243
      Apache 2.0

    • netbox-mcp

      msemino
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that exposes NetBox IPAM data over HTTP, allowing engineers to query subnets, IPs, and VLANs using natural language through AI assistants.
      MIT

    • network_medic

      tanay473
      F
      license
      Not graded
      quality
      D
      maintenance
      Autonomous network monitoring and auto-remediation MCP server for Claude Desktop, enabling observation, planning, human-approved execution, verification, and session summarization.
      1
      -

    • csw-mcp

      chandrapati
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that lets MCP clients such as Cursor and Claude Desktop query a Cisco Secure Workload (Tetration) cluster in plain English. It exposes tools for scopes, sensors, flows, workspaces, policies, and CVE/package vulnerability data, so users can ask posture, blast-radius, and exposure questions without writing HMAC-signed API calls.
      15
      Apache 2.0
    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.5/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct entity (autonomous system, BGP session, internet exchange, etc.) with specific actions (get, list, search). Descriptions are detailed and clarify the scope, leaving no ambiguity between tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., get_autonomous_system, list_bgp_sessions, search_peeringdb). This makes the set predictable and easy to navigate.

    Tool Count5/5

    With 13 tools, the server covers a wide range of peering-related resources without being overwhelming. Each tool serves a clear purpose, and the count feels appropriate for the domain.

    Completeness2/5

    The tools are entirely read-only (get, list, search), lacking any create, update, or delete operations. For a management interface, this is a significant gap that prevents agents from modifying configurations, leading to dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources