Side-by-Side Model Context Protocol Comparison
Dembrandt vs Endiagram MCP
In-depth architectural comparison of the Dembrandt and Endiagram MCP 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
Dembrandt
Developer Tools · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Endiagram MCP
Developer Tools · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Dembrandt if you need specialized Developer Tools tools running via a local process. Choose Endiagram MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
D
Choose Dembrandt when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: Rendered DOM design-token extraction, Focused palette, typography, spacing, and component tools, Baseline drift and findings analysis.
Choose Endiagram MCP when:
- You need dedicated capabilities in the Developer Tools 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. - Primary tools included: structure, invariant, live.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Dembrandt Tools (5)
Rendered DOM design-token extraction
Focused palette, typography, spacing, and component tools
Baseline drift and findings analysis
DTCG, design-document, and report generation
Authenticated, multi-page, mobile, and dark-mode analysis
Endiagram MCP Tools (7)
structure
What is this system? Returns shape (Pipeline, Fork-Join, DAG, Star, Cycle, Tree, Complete, etc.), stages with roles, bridge nodes, cycles, parallelism, critical path, dominator tree, min-cuts, subsystems, interface nodes, actors (who does what, workload entropy), locations (where work happens, boundary crossings). Levers: node=X returns per-node centrality (betweenness, closeness, eigenvector) for a specific node. detect_findings=true flags named structural risks — unguarded-sink (sinks reachable via only pipeline actions, no JOIN/HUB gating), single-cut-path (source-sink pairs with only one vertex-disjoint path), multi-cut-path (paths with redundant defense, min-cut > 1). See server instructions for EN language syntax.
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).
Dembrandt Configuration
Endiagram MCP Configuration