Loppee vs Melta UI
A side-by-side look at the Loppee and Melta UI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Loppee for legal work over a hosted endpoint; 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?
Choose Loppee when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
lookup_business, get_trust_card, get_business_reviews.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 56/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 202 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 5 | 6 |
| Full listing | View Loppee | View Melta UI |
Tools & capabilities
Loppee tools 5
lookup_businessUse this when the user names a business and wants its Loppee Registry match. Returns exact and genuine-prefix name matches with stable ids, coarse public city/state, and truthful Verified, Listed, or Registry disclosure. It does not perform category discovery, accept or return caller location, or return a street address or ZIP.get_trust_cardUse this when a business is already identified and the user wants its public Loppee Trust Card. Returns the exact business status, disclosure, coarse public city/state, public facts, review context, and citation without account authority, street address, ZIP, or signed media links.get_business_reviewsUse this when the user wants the public customer reviews for one Loppee business id. Supports pagination and star-rating filters, preserves reviewer and interaction labels, masks reviewer identity, and changes nothing.explain_recommendationUse this when the user asks why a known published business is or is not recommendable on Loppee. Returns the published class, disclosure, recommendation basis, commercial-neutrality statement, and citation without exposing private weighting.compare_businessesUse this when the user wants a side-by-side comparison of two to twenty known published Loppee business ids. Returns each business's exact class, disclosure, review context, and citation; unknown or unavailable ids are listed as unresolved rather than fabricated.
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.
Loppee
{
"mcpServers": {
"loppee-3": {
"url": "https://loppee.com/mcp/discovery"
}
}
}
Melta UI
{
"mcpServers": {
"melta-ui": {
"command": "npx",
"args": [
"-y",
"melta-ds-mcp"
]
}
}
}
Frequently asked questions
Loppee is categorized under Legal and uses a remote HTTP/SSE transport. Melta UI belongs to Legal and uses a local stdio subprocess. Pick Loppee 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.
Loppee has no declared pricing — check the project's own site. 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 loppee-3 and melta-ui as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Loppee has a quality signal of 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Melta UI has 69/100 (Great) with 4 views, 0 installs and 202 GitHub stars.