First run

Run as stdio (Claude Desktop)

Default transport — no network ports, the MCP client spawns the server as a subprocess.

uv run sdwan-mcp

You should see something like:

[server] SD-WAN Super MCP
[server] Spec version : 20.10
[server] Mode         : READ-ONLY
[server] Transport    : stdio
[server] Auth         : Session
[loader] Loading vmanageapi_2010.json
[loader] Loaded 1 spec file(s), 2230 total paths
[loader] Granularity=section -> 38 tool group(s)
[loader] Mode=RO: kept 1718 operations, filtered out 1265 write operations
[auth] Session login successful
[server] 36 tools registered — starting stdio transport

Run as SSE (network-accessible)

uv run sdwan-mcp --transport sse --host 0.0.0.0 --port 8000

Enable writes

Off by default. Pass --read-write to register POST/PUT/DELETE/PATCH:

uv run sdwan-mcp --read-write

⚠ Writes are real: they mutate your vManage. Don't aim this at production until you've practiced on the DevNet sandbox.

Diff two spec versions

uv run sdwan-mcp --diff 20.10 20.18

Outputs added/removed operations and parameter drift.