Network Sketcher

Network Sketcher is an AI-native network design and diagramming tool. It generates L1/L2/L3 topology diagrams, device tables, and AI-ready context files from structured network data and natural-language workflows.

For MCP users, Network Sketcher Local MCP lets LLM clients such as Cursor and Claude Code design Cisco-style networks directly through Model Context Protocol tool calls. It runs locally over stdio, keeps master files on your machine, and produces SVG / PowerPoint diagrams plus HTML device tables.

If Network Sketcher helps your workflow, please consider starring the repository.

Common use cases:

• Build a 5-site WAN or campus LAN design from an AI conversation
• Generate L1 physical, L2 VLAN/broadcast-domain, and L3 IP topology diagrams
• Export a combined L1/L2/L3 HTML viewer and an interactive device table
• Create an AI Context file so another LLM can review or extend the network design
• Import from live inventory: Use Network Sketcher Cisco Extension converters to turn ACI, Catalyst Center, Catalyst SD-WAN, Meraki, Nexus Dashboard, CML, Cyber Vision, SNA, NetBox exports, or config files (IOS / IOS-XE / NX-OS / IOS-XR / ASA) into CLI commands for any Network Sketcher edition

Quick Start: Local MCP in 3 Steps

The quickest way to try Network Sketcher with an AI agent is the Local MCP edition.

1. Install

git clone https://github.com/cisco-open/network-sketcher/
cd network-sketcher/network-sketcher_local_mcp
python -m pip install -r requirements_mcp.txt

2. Add it to your MCP client

For Cursor, add this to your MCP configuration:

{
  "mcpServers": {
    "network-sketcher": {
      "command": "python",
      "args": [
        "/path/to/network-sketcher/network-sketcher_local_mcp/ns_mcp_server.py"
      ]
    }
  }
}

For Claude Code:

claude mcp add network-sketcher -- python "/path/to/network-sketcher/network-sketcher_local_mcp/ns_mcp_server.py"

Replace /path/to/network-sketcher/ with your local clone path.

3. Ask your agent to build a network

Example prompt:

Using Network Sketcher Local MCP, create a small 5-site WAN design with HQ, two data centers, two branches, Internet and WAN waypoints, edge routers, simple L2 segments, and representative IP addressing. Then build the default L1/L2/L3 diagrams and device table.

The generated files will be saved in your Network Sketcher workspace.

Ecosystem & Integrations

Network Sketcher Local MCP is listed on the official MCP Registry and major MCP platforms:

• Registries: MCP Registry · Glama · PulseMCP
• Hubs: LobeHub

Network Sketcher provides three editions:

• Network Sketcher Local MCP — AI-native MCP server for LLM clients (Cursor, Claude Code, etc.). The most direct AI integration: the LLM calls Network Sketcher tools without a browser or copy-paste.
• Network Sketcher Online — Browser-based web service.
• Network Sketcher Offline — Desktop GUI + CLI. Runs independently with the network-sketcher_offline/ folder alone.

You can use any combination.

network-sketcher/
├── network-sketcher_local_mcp/  # Local MCP edition — MCP server for LLM clients (AI-native)
├── network-sketcher_online/     # Online edition — Web service (browser-based)
├── network-sketcher_offline/    # Offline edition — GUI + CLI (standalone desktop app)
├── README.md
├── LICENSE
└── ...

Extensions: Cisco & Third-Party Converters

The Network Sketcher Cisco Extension repository (Cisco DevNet) is a separate monorepo of converters that turn platform exports or read-only API snapshots into Network Sketcher CLI command scripts (ns_commands.txt). The output works with all three editions — Local MCP, Online, and Offline (GUI / CLI).

Converters: ACI · Catalyst Center · Catalyst SD-WAN · CML · Cyber Vision · Meraki · Nexus Dashboard (NDFC) · Secure Network Analytics · NetBox · template_converter

Learn more: Typical workflow · Tools overview · Third-party converters · Build your own converter

With Local MCP, an AI agent can run a converter, feed ns_commands.txt through run_commands, and finalize with build_default_outputs in one session.

Converter output is a starting draft — see the Cisco Extension README for data-quality caveats and validation guidance.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Network Sketcher Local MCP

AI-native edition: Network Sketcher Local MCP exposes the engine as a Model Context Protocol (MCP) server, enabling LLM clients such as Cursor and Claude Code to drive network design directly. This is the most direct AI integration of the three editions — no browser, no copy-paste.

What is Network Sketcher Local MCP?

Network Sketcher Local MCP is the third edition of Network Sketcher. It wraps network-sketcher_online/ns_engine/ as a library and exposes the Network Sketcher CLI through the Model Context Protocol so that LLM clients can drive network design via Tool calls.

Positioning: The Online edition is "browser + human + LLM (copy-paste)"; the Offline edition is "desktop GUI / CLI"; this edition is "AI-native — the LLM executes the CLI directly".

5min Demo video of the Local MCP edition.

The AI ​​agent Cursor autonomously creates a network using Network Sketcher's Local MCP functionality. It also simultaneously references best practices from other MCPs.

https://github.com/user-attachments/assets/274d5b66-5f4a-407a-bfb5-f71026971fc4

Local MCP Features

• No browser, no copy-paste. The LLM calls add device ... and similar commands as Tool invocations
• Reuses network-sketcher_online/ns_engine/ as a library (no code duplication)
• No changes are made to the existing _online / _offline folders
• stdio transport (designed for local operation)
• Platform import workflow: See Extensions: Cisco & Third-Party Converters above (run_commands + build_default_outputs)

Limitations (Local MCP)