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

All tools are read-only. No write operations are exposed.

Related MCP server: net-mcp

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:

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_server

• list_autonomous_systems: asn, name, affiliated, search

• list_routers: status, platform_id, local_autonomous_system_id

• list_internet_exchanges: status, local_autonomous_system_id, local_autonomous_system_asn

• list_connections: status, internet_exchange_point_id, router_id

• list_routing_policies: type, address_family

• list_communities: type

• search_peeringdb: resource_type (required), search, asn, name

• list_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_sessions merges both types into a single list with common fields and a session_type field ("direct" or "ixp")

• get_bgp_session_detail returns the full type-specific response — direct sessions include relationship, bgp_group, local_ip_address; IXP sessions include ixp_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