junos-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUNOS_SSH_PORT | No | NETCONF port | 830 |
| JUNOS_SSH_USER | Yes | read-only device login user | |
| ORCHESTRATOR_URL | Yes | orchestrator base URL, e.g. https://api.automation.surf.net | |
| JUNOS_SSH_PASSWORD | Yes | device login password | |
| GNMIC_HTTP_BASIC_USER | Yes | Basic Auth user for the targets endpoint | |
| GNMIC_HTTP_BASIC_PASSWORD | Yes | Basic Auth password for the targets endpoint |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List JUNOS device names discovered from the orchestrator gNMI targets endpoint. |
| run_show_commandA | Run a read-only JUNOS 'show' command on a device and return its text output. |
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 2 tools
The two tools have completely distinct purposes: one lists devices, the other runs a show command. There is no ambiguity or overlap between them.
Both tools follow the verb_noun pattern consistently: 'list_devices' and 'run_show_command'.
With only two tools, the server feels very minimal for managing JUNOS devices. It lacks essential operations like configuration or detailed device status beyond show commands.
The server covers only listing devices and running show commands. There are no CRUD operations, configuration management, or filtering capabilities, leaving significant gaps for typical device management tasks.