peering-manager-mcp-server
Related Servers
Alternatives to peering-manager-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that provides access to the PeeringDB peering ecosystem database, enabling AI agents to query peering data through natural language.3 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for FlowSpec that exposes project specifications to Claude Code and other AI tools.32 npm1MIT

NetBox MCP Serverofficial
AlicenseAqualityCmaintenanceRead-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.4231Apache 2.0- AlicenseNot gradedqualityBmaintenanceA 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
- FlicenseNot gradedqualityDmaintenanceAutonomous network monitoring and auto-remediation MCP server for Claude Desktop, enabling observation, planning, human-approved execution, verification, and session summarization.1-
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.1-
TDQS
Scored across 13 tools
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.
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.
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.
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.