Cookie Crumbs Cookie Consent Management vs Melta UI

A side-by-side look at the Cookie Crumbs Cookie Consent Management and Melta UI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Cookie Crumbs   Cookie Consent Management logoCookie Crumbs Cookie Consent ManagementLegal · Local subprocess (stdio)CookieCrumbs is an EU-hosted consent management platform built for people who ship. Run npx cookiecrumbs init and the CLI detects your framework, links the site and writes a typed config. The scanner loads every page in a real browser, in each consent state, and drafts the cookie declaration. The banner holds every tag, pixel and iframe until its category is granted, with Reject all as prominent as Accept all, Google Consent Mode v2 signals and the right rules for the EU, UK, US states, Switzerland, Brazil and Quebec. Every decision lands in a hash-chained consent log with signed exports.71GreatAuth: not declaredMelta UI logoMelta UILegal · Local subprocess (stdio)AI-Ready design system MCP: melta UI tokens, component contracts, 99 rules, check_html self-verify69GreatAuth: not declared

Verdict: choose Cookie Crumbs Cookie Consent Management for legal work as a local process; choose Melta UI for legal as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Cookie Crumbs   Cookie Consent Management logoChoose Cookie Crumbs Cookie Consent Management when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a local stdio subprocess transport.
Explore Cookie Crumbs Cookie Consent Management

Melta UI logoChoose Melta UI when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_token, get_component, check_rule.
Explore Melta UI

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCookie Crumbs   Cookie Consent Management logoCookie Crumbs Cookie Consent ManagementMelta UI logoMelta UI
CategoryLegalLegal
Quality signal71/100 · Great69/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars—202
Directory activity 5 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listed6

Tools & capabilities

Cookie Crumbs Cookie Consent Management tools

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

Melta UI tools 6

  • get_tokenGet a design token by dot-path. Returns the token object with its value and class mapping.
  • get_componentGet component metadata including variants, sizes, accessibility requirements, HTML sample, per-state specs (stateSpecs: disabled/loading/open/empty etc. — each with delta class strings + aria changes), and anatomy parts (overlay/container/th etc. with element/roles/class). Prefer these structured fields over inferring states from the HTML sample.
  • check_ruleCheck class strings against this design system's prohibition rules. Returns violations with reasons and alternatives.
  • check_htmlLint a full HTML/JSX source against melta-ui rules — the same checks as CI and the PostToolUse hook (class rules + html-attr rules + composition rules for HTML). Use this AFTER generating UI code to self-verify before presenting it. Response always includes coverage info (manual rules cannot be auto-checked).
  • searchSearch across tokens and components by keyword. Matches against names, values, class strings, and descriptions. Returns up to 20 results (truncated flag when more matched).
  • get_rulesGet melta-ui prohibition rules from rules.json (107 total). Use this to retrieve manual/contextual rules that check_rule cannot auto-detect. Supports filtering by category, severity, or detector.

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.

Cookie Crumbs Cookie Consent Management

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "cookie-crumbs-cookie-consent-management": {
      "command": "npx",
      "args": [
        "-y",
        "cookiecrumbs"
      ]
    }
  }
}

Melta UI

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "melta-ui": {
      "command": "npx",
      "args": [
        "-y",
        "melta-ds-mcp"
      ]
    }
  }
}

Frequently asked questions

Cookie Crumbs Cookie Consent Management is categorized under Legal and uses a local stdio subprocess. Melta UI belongs to Legal and uses a local stdio subprocess. Pick Cookie Crumbs Cookie Consent Management for legal work and Melta UI for legal.

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.

Cookie Crumbs Cookie Consent Management is listed as free. Melta UI 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 cookie-crumbs-cookie-consent-management and melta-ui as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Cookie Crumbs Cookie Consent Management has a quality signal of 71/100 (Great) with 5 views, 0 installs and 0 GitHub stars. Melta UI has 69/100 (Great) with 4 views, 0 installs and 202 GitHub stars.