Endiagram MCP vs Figwright — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Endiagram MCP vs Figwright
In-depth architectural comparison of the Endiagram MCP and Figwright 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
Endiagram MCP
Architecture & Design · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Figwright
Architecture & Design · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
Verdict Summary: Choose Endiagram MCP if you need specialized Architecture & Design tools running via a local process. Choose Figwright 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 Endiagram MCP 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 have access to required keys: EN_API_URL, ENDIAGRAM_TELEMETRY.
Structural analysis for any system — 12 deterministic graph tools (topology, bottlenecks, blast radius, trace, diff, centrality) from EN syntax descriptions. No AI inside the computation. Install: npx @endiagram/mcp
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.
rules` (one per line) checks custom claims. Four supported shapes: `no bridge that is also hub` · `every path from X to Y passes through at least one of [A,B,C]` (precedence) · `no node with centrality above N` · `removing any single node disconnects at most N others`.
live
—
reachable
defense_nodes=a,b,c` checks whether guards cover every path.
Endiagram MCP is categorized under Architecture & Design and uses a local stdio subprocess. In contrast, Figwright belongs to Architecture & Design using local stdio subprocess. Select Endiagram MCP when you need capabilities focused on architecture & design and Figwright when you require tools for architecture & design.
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).
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…