Dembrandt vs UI Beats

A side-by-side look at the Dembrandt and UI Beats 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 declaredUI Beats logoUI BeatsDeveloper Tools · Local subprocess (stdio)MCP server for UI Beats. Let your coding agent search, read and install animated React components.49FairAuth: not declared

Verdict: choose Dembrandt for developer tools work as a local process; choose UI Beats 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

UI Beats logoChoose UI Beats when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDembrandt logoDembrandtUI Beats logoUI Beats
CategoryDeveloper ToolsDeveloper Tools
Quality signal53/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3,749234
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.

UI Beats 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"
      ]
    }
  }
}

UI Beats

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ui-beats": {
      "command": "npx",
      "args": [
        "-y",
        "shadcn@latest"
      ]
    }
  }
}

Frequently asked questions

Dembrandt is categorized under Developer Tools and uses a local stdio subprocess. UI Beats belongs to Developer Tools and uses a local stdio subprocess. Pick Dembrandt for developer tools work and UI Beats 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. UI Beats has no declared pricing — check the project's own site. 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 ui-beats 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,749 GitHub stars. UI Beats has 49/100 (Fair) with 0 views, 0 installs and 234 GitHub stars.