Nokia SR OS gNMI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sros_connectA | Connect to a Nokia SR OS device via gNMI (gRPC). Registers a named session with credentials for subsequent operations. Default port is 57400. TLS certificate verification is enabled by default. |
| sros_disconnectC | Close a gNMI session to a Nokia SR OS device. |
| sros_get_configA | Get configuration from Nokia SR OS via gNMI Get (datatype=config). Provide one or more YANG paths. Uses json_ietf encoding. Nokia SROS YANG path examples: /configure/router[router-name=Base]/interface /configure/port[port-id=1/1/c2/1] /configure/service/vprn[service-name=CUST-1] /configure/router[router-name=Base]/bgp /configure/card[slot-number=1] /configure (entire config) |
| sros_get_stateA | Get operational state from Nokia SR OS via gNMI Get (datatype=state). Provide one or more YANG paths. Uses json_ietf encoding. Nokia SROS state path examples: /state/router[router-name=Base]/interface[interface-name=to-pe2] /state/port[port-id=1/1/c2/1] /state/router[router-name=Base]/bgp/neighbor /state/card[slot-number=1] /state/system/information |
| sros_set_updateA | Update (merge) configuration on Nokia SR OS via gNMI Set. Provide a YANG path and JSON value to merge. Example — create interface: path: /configure/router[router-name=Base]/interface[interface-name=lo0] value: {"ipv4": {"primary": {"address": "10.0.0.1", "prefix-length": 32}}} Example — enable port: path: /configure/port[port-id=1/1/c2/1] value: {"admin-state": "enable"} |
| sros_set_replaceA | Replace configuration on Nokia SR OS via gNMI Set. Replaces the entire subtree at the given path with the provided value. WARNING: This removes any existing config under the path that is not in the new value. |
| sros_set_deleteA | Delete configuration on Nokia SR OS via gNMI Set. Removes the config subtree at the given path(s). Example: paths: ['/configure/router[router-name=Base]/interface[interface-name=test]'] |
| sros_capabilitiesB | Get gNMI capabilities from Nokia SR OS device. Returns supported encodings, YANG models, and gNMI version. |
| sros_list_sessionsB | List all active Nokia SR OS gNMI sessions. |
| yang_searchA | Search Nokia SR OS YANG paths by keyword. Use this to find the correct gNMI path before using sros_get_config/sros_get_state/sros_set_update. Examples: yang_search('fpe', 'configure') → find FPE paths yang_search('end-dt2', 'configure') → find SRv6 EVPN function paths yang_search('bgp-evpn', 'configure') → find EVPN BGP paths yang_search('pxc', 'configure') → find Port Cross-Connect paths yang_search('neighbor', 'state') → find BGP neighbor state paths Requires YANG models in yang/sros-25.10/YANG/ or pre-built cache in yang/cache/. |
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 10 tools
Each tool has a clearly distinct purpose: session lifecycle, YANG path discovery, config/state retrieval, set variants, and capabilities. The get_config vs get_state and set_update/replace/delete distinctions are explicit in both names and descriptions. No meaningful overlap or ambiguous boundaries exist.
Nine of ten tools use the consistent sros_ prefix with verb_or_noun naming, making the set mostly predictable. The exception is yang_search, which breaks the sros_ pattern but remains clear. This is a minor deviation rather than a pattern failure.
Ten tools is well-scoped for a gNMI configuration and state management server. Each tool earns its place, covering connection handling, path discovery, retrieval, mutation, and capabilities without bloat. The count is neither thin nor excessive.
The surface covers gNMI Capabilities, Get (config and state), Set (update, replace, delete), session lifecycle, and YANG path discovery. The major missing operation is gNMI Subscribe for streaming telemetry, which is a core gNMI RPC. This is a notable but not fatal gap for configuration-focused workflows.