Dembrandt vs Roast My Design System

A side-by-side look at the Dembrandt and Roast My Design System 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 declaredRoast My Design System logoRoast My Design SystemDeveloper Tools · Local subprocess (stdio)Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.49FairAuth: no auth required

Verdict: choose Dembrandt for developer tools work as a local process; choose Roast My Design System 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

Roast My Design System logoChoose Roast My Design System 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 Roast My Design System

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDembrandt logoDembrandtRoast My Design System logoRoast My Design System
CategoryDeveloper ToolsDeveloper Tools
Quality signal53/100 · Good49/100 · Fair
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,80627
Directory activity 1 views 0 installs 0 upvotes 1 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.

Roast My Design System 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"
      ]
    }
  }
}

Roast My Design System

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "roast-my-design-system": {
      "command": "npx",
      "args": [
        "-y",
        "roast-my-design-system@latest"
      ]
    }
  }
}

Frequently asked questions

Dembrandt is categorized under Developer Tools and uses a local stdio subprocess. Roast My Design System belongs to Developer Tools and uses a local stdio subprocess. Pick Dembrandt for developer tools work and Roast My Design System 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. Roast My Design System 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 roast-my-design-system 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,806 GitHub stars. Roast My Design System has 49/100 (Fair) with 1 views, 0 installs and 27 GitHub stars.