peering-manager-mcp-server
A read-only MCP server for Peering Manager that exposes BGP sessions, autonomous systems, routers, IXPs, and other peering infrastructure data as conversational tools for Claude and other MCP clients.
README
Peering Manager MCP Server
A read-only Model Context Protocol server for Peering Manager. Exposes peering infrastructure data as conversational tools for use with Claude Code, claude.ai, or any MCP-compatible client.
Tools
| Tool | Description |
|---|---|
list_bgp_sessions |
Unified view of BGP sessions across direct peering and IXP sessions |
get_bgp_session_detail |
Full detail for a single session with type-specific fields |
list_autonomous_systems |
Search/filter autonomous systems |
get_autonomous_system |
AS detail with shared IXPs and facilities |
list_routers |
Routers with status and platform info |
list_internet_exchanges |
Internet exchange points |
get_internet_exchange |
IXP detail with available peers |
list_connections |
IXP connections with IP/VLAN/router mapping |
list_routing_policies |
Import/export routing policies |
list_communities |
BGP communities |
get_router_configuration |
Rendered Jinja2 configuration for a router |
search_peeringdb |
Query cached PeeringDB data (networks, IXPs, facilities, network-ixlans) |
list_changes |
Audit log of recent object changes |
All tools are read-only. No write operations are exposed.
Requirements
- Node.js 18+
- A running Peering Manager instance with API access
- An API token with read permissions
Install
npm install -g git+https://github.com/yourorg/peering-manager-mcp-server.git
This installs the peering-manager-mcp-server command globally.
Configuration
The server reads two required environment variables:
| Variable | Description |
|---|---|
PM_URL |
Base URL of your Peering Manager instance (e.g. https://pm.example.com) |
PM_API_TOKEN |
API token for authentication |
PM_CONFIG_TIMEOUT |
Optional. Timeout in seconds for config rendering (default: 120) |
Usage
Claude Code
Add to your global MCP settings (~/.claude/settings.json):
{
"mcpServers": {
"peering-manager": {
"command": "peering-manager-mcp-server",
"env": {
"PM_URL": "https://pm.example.com",
"PM_API_TOKEN": "your-api-token"
}
}
}
}
MCP Inspector
PM_URL=https://pm.example.com PM_API_TOKEN=your-token npx @modelcontextprotocol/inspector peering-manager-mcp-server
Development
git clone https://github.com/yourorg/peering-manager-mcp-server.git
cd peering-manager-mcp-server
npm install
npm run build
PM_URL=https://pm.example.com PM_API_TOKEN=your-token npm start
Example queries
Once connected, you can ask Claude things like:
- "Which BGP sessions are not established?"
- "Show me all peers at AMS-IX"
- "What IXPs do we share with AS13335?"
- "Show me the config for router core-1"
- "What routing policies are applied to our transit peers?"
- "What changed in the last week?"
Filtering and pagination
All list tools accept limit (default 100, max 1000) and offset for pagination. Responses include total_count so you know when there are more results.
Session-specific filters:
list_bgp_sessions:asn,router,ixp,status,bgp_state,address_family,is_route_serverlist_autonomous_systems:asn,name,affiliated,searchlist_routers:status,platform_id,local_autonomous_system_idlist_internet_exchanges:status,local_autonomous_system_id,local_autonomous_system_asnlist_connections:status,internet_exchange_point_id,router_idlist_routing_policies:type,address_familylist_communities:typesearch_peeringdb:resource_type(required),search,asn,namelist_changes:action,changed_object_type,user,time_after,time_before
BGP session model
Peering Manager stores direct peering sessions and IXP peering sessions as separate models. This server unifies them:
list_bgp_sessionsmerges both types into a single list with common fields and asession_typefield ("direct"or"ixp")get_bgp_session_detailreturns the full type-specific response — direct sessions includerelationship,bgp_group,local_ip_address; IXP sessions includeixp_connection,is_route_server,exists_in_peeringdb
Timeouts
Most API calls use a 30-second timeout. get_router_configuration uses 120 seconds by default (configurable via PM_CONFIG_TIMEOUT) because config rendering may involve Jinja2 template processing and IRR/AS-SET lookups.
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.