Skip to main content
Glama
peering-manager-mcp-server

peering-manager-mcp-server

by fmcglinn

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.

Related MCP server: flowspec-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:

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_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

Available Tools

13 tools
get_autonomous_systemA

Get full detail for an autonomous system including shared IXPs and shared facilities.

Inputs: id (required).

get_bgp_session_detailA

Get full detail for a single BGP session. Returns type-specific fields based on session type.

Inputs: id (required), session_type (required).

get_internet_exchangeA

Get full detail for an internet exchange point including available peers.

Inputs: id (required).

get_router_configurationA

Get the rendered configuration for a specific router. Uses extended timeout due to Jinja2 rendering and possible IRR lookups.

Inputs: id (required).

list_autonomous_systemsB

List autonomous systems configured in Peering Manager.

Inputs: asn, name, limit, offset, +2 more.

list_bgp_sessionsA

List BGP sessions across both direct peering and IXP sessions. Returns unified view with common fields.

Inputs: asn, ixp, limit, offset, +5 more.

list_changesB

List recent object changes from the Peering Manager audit log.

Inputs: user, limit, action, offset, +3 more.

list_communitiesB

List BGP communities configured in Peering Manager.

Inputs: type, limit, offset.

list_connectionsB

List IXP connections with IP/VLAN/router mapping.

Inputs: limit, offset, status, router_id, +1 more.

list_internet_exchangesC

List internet exchange points configured in Peering Manager.

Inputs: limit, offset, status, local_autonomous_system_id, +1 more.

list_routersB

List routers configured in Peering Manager.

Inputs: limit, offset, status, platform_id, +1 more.

list_routing_policiesA

List routing policies configured in Peering Manager.

Inputs: type, limit, offset, address_family.

search_peeringdbA

Search cached PeeringDB data. Supports networks, internet-exchanges, facilities, and network-ixlans.

Inputs: resource_type (required), asn, name, limit, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers