Verified

Routing Director MCP Server

Juniper Routing Director platform access for network routing and KPI monitoring.

Data last scanned today · Reviewed today

45★ 4PythonApache-2.0

Overview

Routing Director MCP Server facilitates direct interaction with the Juniper Routing Director ecosystem. It enables AI models to perform tasks such as device management, configuration template deployment, and VPN service administration through the Model Context Protocol. Beyond basic management, the server provides tools for network topology visualization and observability, including KPI monitoring. Users can filter exposed capabilities by specific components like ems for alarm handling or device-kpi for exception event tracking.

Our verdict

With a security score of 35/100, this server is currently classified as high-risk. The score reflects that the server is community-maintained rather than official and lacks an independent editorial review. Given that critical authentication methods and read-only modes have not been verified, it is recommended only for testing environments by experienced network engineers familiar with their Routing Director deployment.

Zero direct dependencies minimizes the supply-chain surface area.
Supports both basic and token-based authentication methods.
Compatible with both HTTP and stdio transport protocols.
Provides documented filtering for specific API components.

Security-sensitive features lack independent editorial review.
Not maintained by the official vendor.
High risk level due to unreviewed authentication implementations.

Compatibility

Client	Local	Docker	Remote	Read-only
ChatGPT
Claude Desktop
Cursor
VS Code
Windsurf

Frequently asked questions

›What are the Python version requirements for running this server?

The server requires Python version 3.10 through 3.14.

›Which transport protocols are supported?

The server supports both HTTP and stdio transport protocols.

›How can I filter the tools and capabilities exposed by the server?

You can use the optional components field in your config.json file to filter the specification for specific areas like alarms (ems), device syslog (juniper-resiliency-interface), or KPI exception events (device-kpi).

›Is authentication required between the MCP server and an MCP client?

Authentication is supported for HTTP transports via a .tokens file, while it is bypassed for stdio transport since it is typically used in secure local environments.

›What authentication methods does the server support for connecting to the Routing Director platform?

The server supports both basic authentication with a username and password or token-based authentication using an API token.