Dembrandt vs Erd Editor

A side-by-side look at the Dembrandt and Erd Editor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Dembrandt logoDembrandtDeveloper Tools · Local subprocess (stdio)Design tokens from any live site: colours, type, spacing, components, drift against a baseline.53GoodAuth: not declaredErd Editor logoErd EditorDeveloper Tools · Local subprocess (stdio)Design database schemas as ERDs in your browser, VS Code, JetBrains IDEs or Obsidian. Import SQL, DBML and GraphQL, export DDL and code, and let coding agents edit live over MCP.61GoodAuth: no auth required

Verdict: choose Dembrandt for developer tools work as a local process; choose Erd Editor for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Dembrandt logoChoose Dembrandt when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore Dembrandt

Erd Editor logoChoose Erd Editor when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Erd Editor

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDembrandt logoDembrandtErd Editor logoErd Editor
CategoryDeveloper ToolsDeveloper Tools
Quality signal53/100 · Good61/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3,7781,728
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Dembrandt tools

No tool names declared yet. Check the project README from the listing page.

Erd Editor tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Dembrandt

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dembrandt": {
      "command": "npx",
      "args": [
        "-y",
        "dembrandt"
      ]
    }
  }
}

Erd Editor

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "erd-editor": {
      "command": "npx",
      "args": [
        "-y",
        "@dineug/erd-editor-mcp"
      ]
    }
  }
}

Frequently asked questions

Dembrandt is categorized under Developer Tools and uses a local stdio subprocess. Erd Editor belongs to Developer Tools and uses a local stdio subprocess. Pick Dembrandt for developer tools work and Erd Editor for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Dembrandt has no declared pricing — check the project's own site. Erd Editor is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add dembrandt and erd-editor as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Dembrandt has a quality signal of 53/100 (Good) with 1 views, 0 installs and 3,778 GitHub stars. Erd Editor has 61/100 (Good) with 0 views, 0 installs and 1,728 GitHub stars.