junos-mcp-server
Enables read-only troubleshooting of JUNOS devices by running show commands over NETCONF, with dynamic device discovery from an orchestrator.
README
junos-mcp-server
Read-only JUNOS troubleshooting MCP server. Discovers devices dynamically from
the SURF orchestrator's gNMI-targets endpoint and runs show commands only
over NETCONF (PyEZ). It has no configuration/write capability by design.
Tools
list_devices()— device names from the orchestrator.run_show_command(device, command)— runs ashowcommand; rejects anything else.
Environment
| Var | Required | Default | Purpose |
|---|---|---|---|
ORCHESTRATOR_URL |
yes¹ | — | orchestrator base URL, e.g. https://api.automation.surf.net |
GNMIC_HTTP_BASIC_USER |
yes¹ | — | Basic Auth user for the targets endpoint |
GNMIC_HTTP_BASIC_PASSWORD |
yes¹ | — | Basic Auth password for the targets endpoint |
JUNOS_SSH_USER |
yes | — | read-only device login user |
JUNOS_SSH_PASSWORD |
yes | — | device login password |
JUNOS_SSH_PORT |
no | 830 |
NETCONF port |
JUNOS_DEV_MODE |
no | 0 |
development mode — serve JUNOS_DEV_TARGETS instead of querying the orchestrator |
JUNOS_DEV_TARGETS |
dev² | [] |
JSON list of node hostnames, e.g. ["r1.lab.net","r2.lab.net"] |
¹ Not required when JUNOS_DEV_MODE is set. ² Required (non-empty) when JUNOS_DEV_MODE is set.
Development mode
Set JUNOS_DEV_MODE=1 and JUNOS_DEV_TARGETS to a JSON list of your own nodes
to bypass the orchestrator entirely — list_devices() then returns exactly that
list and run_show_command connects to those hostnames. SSH credentials are
still required; orchestrator/Basic-Auth vars are not.
JUNOS_DEV_MODE=1 JUNOS_DEV_TARGETS='["r1.lab.net","r2.lab.net"]' \
JUNOS_SSH_USER=ro JUNOS_SSH_PASSWORD=... uvx --from . junos-mcp-server
Run
uvx --from . junos-mcp-server # from a local checkout
uvx --from git+<repo-url> junos-mcp-server # from git
MCP client config (stdio)
{
"mcpServers": {
"junos": {
"command": "uvx",
"args": ["--from", "git+<repo-url>", "junos-mcp-server"],
"env": {
"ORCHESTRATOR_URL": "https://api.automation.surf.net",
"GNMIC_HTTP_BASIC_USER": "gnmic",
"GNMIC_HTTP_BASIC_PASSWORD": "...",
"JUNOS_SSH_USER": "...",
"JUNOS_SSH_PASSWORD": "..."
}
}
}
}
Requires NETCONF enabled on devices (set system services netconf ssh).
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.