Cisco NSO MCP Server

Created By
dbono711a year ago
A Model Context Protocol (MCP) server implementation for Cisco NSO that enables AI-powered network automation through natural language interactions.
Overview

What is Cisco NSO MCP Server?

Cisco NSO MCP Server is a Model Context Protocol (MCP) server implementation for Cisco NSO that enables AI-powered network automation through natural language interactions.

How to use Cisco NSO MCP Server?

To use the Cisco NSO MCP Server, install it via pip and run it as a command-line tool. You can connect to the server using either stdio or SSE transport methods.

Key features of Cisco NSO MCP Server?

  • Tool-first design for network operations
  • Asynchronous processing for better performance
  • Standardized tool definition, discovery, and execution
  • Context management for efficient communication between tools and models
  • Supports multiple AI frameworks including OpenAI and Anthropic

Use cases of Cisco NSO MCP Server?

  1. Automating network configurations through natural language commands.
  2. Integrating AI models with network management tools.
  3. Providing a standardized interface for various automation needs.

FAQ from Cisco NSO MCP Server?

  • Can I use Cisco NSO MCP Server without an LLM?

Yes! The MCP framework is LLM-agnostic and can be used directly in any application.

  • What programming language is Cisco NSO MCP Server written in?

It is written in Python and requires Python 3.13 or higher.

  • Is there a license for Cisco NSO MCP Server?

Yes, it is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dbono711
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago