Figwright vs Network Sketcher — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Figwright vs Network Sketcher
In-depth architectural comparison of the Figwright and Network Sketcher MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Figwright
Architecture & Design · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Network Sketcher
Architecture & Design · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Figwright if you need specialized Architecture & Design tools running via a local process. Choose Network Sketcher if your workspace requires Architecture & Design integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Figwright when:
You need dedicated capabilities in the Architecture & Design domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Architecture & Design domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Generates L1/L2/L3 topology diagrams in SVG and PowerPoint formats, Produces interactive HTML device tables, Creates AI-ready context files for further LLM processing.
Bidirectional Figma server over a local WebSocket relay: turn a selection into framework-aware code (reusing your components and tokens), or author frames, text, styles, variables, and whole screens back onto the canvas. 92 tools, any MCP client, no Dev Mode seat or paid tier.
Local-first MCP server for AI-driven network design. Creates Cisco-style network master files, L1/L2/L3 topology diagrams, combined HTML viewers, device tables, and AI Context files.
Category & Scope
Tools & Capabilities Breakdown
Figwright Tools (3)
Read
selection, document and node inspection, styles, variables, components, fonts, reactions, motion (animation) state, screenshots, original image-fill assets, PDF export, and video export of animated frames (MP4 / GIF / WebM); plus `list_files` / `use_file` for working across more than one open Figma…
Write
create and edit frames, text, shapes, auto-layout, effects, styles, variables, components (including authoring their boolean/text/instance-swap properties), pages, reactions, and Motion animations (keyframes, animation-style presets, timelines); plus a `batch` tool to apply many edits at once.
Grounding
`get_design_context` for faithful, de-duplicated design context, and `component_map` / `token_map` / `icon_map`, which join Figma data to your codebase so codegen reuses what you already have; plus `design_diff`, which reports what changed in a design against a saved baseline so you update only the…
Network Sketcher Tools (6)
Generates L1/L2/L3 topology diagrams in SVG and PowerPoint formats
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Figwright is categorized under Architecture & Design and uses a local stdio subprocess. In contrast, Network Sketcher belongs to Architecture & Design using local stdio subprocess. Select Figwright when you need capabilities focused on architecture & design and Network Sketcher when you require tools for architecture & design.