catalyst-sdwan-super-mcp¶
A FastMCP server that exposes the Cisco Catalyst SD-WAN Manager (vManage) REST API as MCP tools, so any MCP-compatible LLM client (Claude Desktop, Claude Code, Cursor, …) can query and manage your SD-WAN overlay.
Tools are generated dynamically from the official OpenAPI specs — drop in a new spec, the tools rebuild themselves. No code changes per vManage version.
At a glance¶
- Dynamic — no codegen step, no per-version Python file.
- Adaptive tool splitting — a size cap (
max_actions_per_tool, default 150) drives section / sub-tag / URL-path recursion so every tool stays under budget. 360 tools on 20.18 RW out of the box. How it works. - Read-only by default — explicit
--read-writeflag for POST/PUT/DELETE/PATCH. - Two auth modes to vManage — modern JWT (20.18.1+) and legacy session (older).
- Three transports — stdio (Claude Desktop), SSE, streamable-HTTP. HTTP transports ship with first-class bearer-token auth and auto-demote non-loopback binds to
127.0.0.1when unauthenticated. HTTP auth. - Response pagination — auto-follow for scroll- and offset-style bulk endpoints, with resumable cursors. Pagination.
- Configurable retry + timeout — exponential-backoff retry of transient 5xx and connection errors. Configuration.
- Auto-fetch specs — bump
active_version, the loader pulls and stitches the matching OpenAPI spec fromdeveloper.cisco.comon startup. Spec versions. - Version diff —
sdwan-mcp --diff 20.15 20.18shows added/removed/changed operations before upgrading.
What's the “super” for?¶
Instead of hand-writing a tool per endpoint (the API has 2,000+), we derive everything from the upstream spec. Cisco evolves vManage; you drop the new spec in specs/{version}/ and the MCP tools rebuild themselves.
Continue reading¶
- Install
- First run
- DevNet sandbox — the easiest way to try it without a vManage of your own
- Architecture overview