Cisco Catalyst Sdwan Mcp Server

Created By
stormbliss10 months ago
A comprehensive Model Context Protocol (MCP) server for monitoring and managing SD-WAN devices through REST API endpoints. This server exposes SD-WAN device monitoring and management functionality that can be integrated with Cursor and other MCP-compatible tools.
Overview

What is Cisco Catalyst SD-WAN MCP Server?

Cisco Catalyst SD-WAN MCP Server is a comprehensive Model Context Protocol (MCP) server designed for monitoring and managing SD-WAN devices through REST API endpoints. It provides functionalities that can be integrated with Cursor and other MCP-compatible tools.

How to use Cisco Catalyst SD-WAN MCP Server?

To use the server, set up the environment by configuring the Python path and run the main script. You can authenticate with the SD-WAN management server and utilize various monitoring and management tools provided by the server.

Key features of Cisco Catalyst SD-WAN MCP Server?

  • Device Management: List and monitor SD-WAN fabric devices
  • Statistics Collection: Interface statistics, device counters, tunnel statistics
  • BFD Monitoring: Monitor Bidirectional Forwarding Detection state and sessions
  • Configuration Access: Retrieve device configurations
  • Advanced Analytics: Health summaries, traffic analysis, and alerting
  • Session Management: Automatic authentication and session handling
  • Async Support: Full async/await support for non-blocking operations
  • Cursor Integration: Seamless integration with Cursor IDE

Use cases of Cisco Catalyst SD-WAN MCP Server?

  1. Monitoring the health and performance of SD-WAN devices.
  2. Managing configurations and retrieving statistics for SD-WAN networks.
  3. Integrating with other tools for enhanced SD-WAN management.

FAQ from Cisco Catalyst SD-WAN MCP Server?

  • What programming language is used for the server?

The server is built using Python and requires Python 3.8 or higher.

  • Can I integrate this server with other tools?

Yes! The server is designed to integrate seamlessly with Cursor and other MCP-compatible tools.

  • Is there support for asynchronous operations?

Yes! The server supports full async/await functionality for non-blocking operations.

Server Config

{
  "mcpServers": {
    "sdwan-mcp-server": {
      "command": "python",
      "args": [
        "/path/to/your/project/main.py"
      ],
      "env": {
        "PYTHONPATH": "/path/to/your/project"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
stormbliss
Star
-
Language
-
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