Melta UI vs Magic MCP
A side-by-side look at the Melta UI and Magic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Melta UI for legal work as a local process; choose Magic MCP for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 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.
Choose Magic MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TWENTY_FIRST_API_KEY, API_KEY_21ST.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Architecture & Design |
| Quality signal | 68/100 · Great | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | TWENTY_FIRST_API_KEYAPI_KEY_21ST |
| Verified owner | Community listing | Community listing |
| GitHub stars | 202 | 6,193 |
| Directory activity | 3 views 0 installs 0 upvotes | 16 views 1 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Melta UI | View Magic MCP |
Tools & capabilities
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.
Magic MCP 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.
Melta UI
{
"mcpServers": {
"melta-ui": {
"command": "npx",
"args": [
"-y",
"melta-ds-mcp"
]
}
}
}
Magic MCP
{
"mcpServers": {
"21st-dev-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@21st-dev/cli@latest"
],
"env": {
"TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
"API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
}
}
}
}
Frequently asked questions
Melta UI is categorized under Legal and uses a local stdio subprocess. Magic MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Melta UI for legal work and Magic MCP for architecture & design.
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.
Melta UI has no declared pricing — check the project's own site. Magic MCP is listed as a paid service. Auth: api key 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 melta-ui and 21st-dev-magic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Melta UI has a quality signal of 68/100 (Great) with 3 views, 0 installs and 202 GitHub stars. Magic MCP has 53/100 (Good) with 16 views, 1 installs and 6,193 GitHub stars.