MCP server integrating with Juniper Routing Director
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"routing-director-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
<!-- mcp-name: io.github.Juniper/routing-director-mcp-server --> # Routing Director MCP Server An MCP (Model Context Protocol) server that integrates with Juniper's Routing Director platform, providing intelligent access to network routing, assurance, optimization, and intelligence capabilities. ## Features - Flexible Authentication: Supports both basic and token-based authentication - Multiple Transport Options: HTTP and stdio transport protocols - Device management and monitoring - Configuration template deployment - VPN service management - Network topology visualization - KPI monitoring and observability - Customer and organization management ## Prerequisites - Python 3.10 or 3.11 - Juniper Routing Director instance - Network connectivity to Routing Director API - Valid Routing Director credentials (username/password or API token) ## Installation ### From Source ```bash git clone https://github.com/Juniper/routing-director-mcp-server.git cd routing-director-mcp-server python -m venv .venv source .venv/bin/activate # On Windows: .venv\Scripts\activate pip install -r requirements.txt ``` ### From MCP Registry TBD ## Configuration ### Configuration File (config.json) Create a `config.json` file with the following structure: **Basic Authentication:** ```json { "http_url": "https://your-routing-director-host/", "org_id": "your-organization-id", "auth": { "type": "basic", "username": "your-username@example.com", "password": "your-password" } } ``` **Token Authentication:** ```json { "http_url": "https://your-routing-director-host/", "org_id": "your-organization-id", "auth": { "type": "token", "token": "your-api-token" } } ``` Note: This authentication is between the MCP server and the Routing Director instance. The MCP server will handle authentication with Routing Director on behalf of clients connecting to it. ### Configuration Parameters - **http_url** (required): URL of your Routing Director instance - **or…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.