Skip to main content
Glama

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 a show command; rejects anything else.

Related MCP server: network-mcp

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).

Install Server
A
license - permissive license
A
quality
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    -
    quality
    A
    maintenance
    Enables LLM interactions with Juniper Junos network devices, allowing natural language access to device configuration, monitoring, and management operations through secure SSH connections.
    103
    Apache 2.0
  • A
    license
    -
    quality
    D
    maintenance
    Provides AI assistants with direct access to multi-vendor network devices for tasks like configuration management, health checks, and topology discovery through 35 specialized tools. It enables natural language control over platforms including Cisco, Juniper, and Nokia using SSH, NETCONF, and SNMP protocols.
    11
    MIT
  • A
    license
    -
    quality
    D
    maintenance
    Enables interaction with Cisco NX-OS devices by executing CLI commands via the NX-API interface. It supports concurrent multi-device operations, batch command execution, and provides responses in both text and structured JSON formats.
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    Enables LLMs to run read-only show commands on Cisco IOS/IOS-XE and Nexus switches over SSH, with a two-account model for privilege separation and a fail-closed allowlist for safety.
    25

View all related MCP servers

Related MCP Connectors

  • Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.

  • Issue, rotate and revoke scoped API-key passes for 25+ providers — the agent never sees a real key

  • Deploy apps on your cloud. Create environments, configure infrastructure, and monitor jobs.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/workfloworchestrator/junos-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server