Cisco Nso MCP Server

[Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) is an open protocol that standardizes how AI models interact with

Local serverstdioPython

What is the Cisco Nso MCP server?

Most developer tooling work still happens through a UI a human drives. Cisco Nso MCP server moves it into the conversation instead. Model Context Protocol (MCP) is an open protocol that standardizes how AI models interact with external tools and services. MCP enables:.

The short version

  • Stdio Transport — By default, this MCP server uses stdio transport for process-bound communication
  • Tool-First Design — Network operations are defined as discrete tools with clear interfaces
  • Asynchronous Processing — All network operations are implemented asynchronously for better performance
  • Structured Responses — Consistent response format with status, data, and metadata sections
  • Environment Resources — Provides contextual information about the NSO environment
  • NSO Integration — Uses cisco-nso-restconf library for a clean, Pythonic interface to NSO's RESTCONF API

Getting it running

Installation goes through your MCP client rather than a global install: point it at cisco-nso-mcp-server on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 11 tools. What each one is for:

  • get_device_ned_ids — Retrieves Network Element Driver (NED) IDs from Cisco NSO
  • get_device_groups — Retrieves device groups from Cisco NSO
  • get_device_platform — Gets platform information for a specific device in Cisco NSO
  • get_device_config — Gets full configuration for a specific device in Cisco NSO
  • get_device_state — Gets state for a specific device in Cisco NSO
  • check_device_sync — Checks sync status for a specific device in Cisco NSO
  • sync_from_device — Syncs from a specific device in Cisco NSO
  • get_service_types — Gets service types in Cisco NSO
  • get_services — Gets services for a specific service type in Cisco NSO
  • Tools — The Tools tool exposed by this server
  • Resources — The Resources tool exposed by this server

What it needs from you

Configuration is passed through the environment: LOG_FILE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Python 3.12+ - Cisco NSO with RESTCONF API enabled - Network connectivity to NSO RESTCONF API

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Cisco Nso.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cisco Nso's toolset — get_device_ned_ids, get_device_groups, get_device_platform and 8 more — is a fair guide to whether it matches your workflow. It is maintained by dbono711; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cisco Nso's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
get_device_ned_idsRetrieves Network Element Driver (NED) IDs from Cisco NSO
get_device_groupsRetrieves device groups from Cisco NSO
get_device_platformGets platform information for a specific device in Cisco NSO
get_device_configGets full configuration for a specific device in Cisco NSO
get_device_stateGets state for a specific device in Cisco NSO
check_device_syncChecks sync status for a specific device in Cisco NSO
sync_from_deviceSyncs from a specific device in Cisco NSO
get_service_typesGets service types in Cisco NSO
get_servicesGets services for a specific service type in Cisco NSO
ToolsThe Tools tool exposed by this server.
ResourcesThe Resources tool exposed by this server.

How to install the Cisco Nso MCP server

{
  "mcpServers": {
    "nso": {
      "command": "uvx",
      "args": [
        "cisco-nso-mcp-server",
        "--nso-address=127.0.0.1",
        "--nso-port=8080",
        "--nso-username=admin",
        "--nso-password=admin"
      ],
      "env": {
        "LOG_FILE": "/path/to/your/logs/nso-mcp.log"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Python 3.12+ - Cisco NSO with RESTCONF API enabled - Network connectivity to NSO RESTCONF API
VariableDescriptionRequired
LOG_FILEConfiguration value read at startup.Optional

Example prompts to try

  • Use Cisco Nso to get device ned ids.
  • Use Cisco Nso to get device groups.
  • Use Cisco Nso to get device platform.

Frequently asked questions

It connects Cisco Nso to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (get_device_ned_ids, get_device_groups, get_device_platform, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cisco Nso directly.