peering-manager-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PM_URL | Yes | Base URL of your Peering Manager instance (e.g. https://pm.example.com) | |
| PM_API_TOKEN | Yes | API token for authentication | |
| PM_CONFIG_TIMEOUT | No | Optional. Timeout in seconds for config rendering (default: 120) | 120 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_bgp_sessionsA | List BGP sessions across both direct peering and IXP sessions. Returns unified view with common fields. |
| get_bgp_session_detailA | Get full detail for a single BGP session. Returns type-specific fields based on session type. |
| list_autonomous_systemsB | List autonomous systems configured in Peering Manager. |
| get_autonomous_systemA | Get full detail for an autonomous system including shared IXPs and shared facilities. |
| list_routersB | List routers configured in Peering Manager. |
| list_internet_exchangesC | List internet exchange points configured in Peering Manager. |
| get_internet_exchangeA | Get full detail for an internet exchange point including available peers. |
| list_connectionsB | List IXP connections with IP/VLAN/router mapping. |
| list_routing_policiesA | List routing policies configured in Peering Manager. |
| list_communitiesB | List BGP communities configured in Peering Manager. |
| get_router_configurationA | Get the rendered configuration for a specific router. Uses extended timeout due to Jinja2 rendering and possible IRR lookups. |
| search_peeringdbA | Search cached PeeringDB data. Supports networks, internet-exchanges, facilities, and network-ixlans. |
| list_changesB | List recent object changes from the Peering Manager audit log. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.