Melta UI vs Processos TRT (Justiça do Trabalho)
A side-by-side look at the Melta UI and Processos TRT (Justiça do Trabalho) 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 Processos TRT (Justiça do Trabalho) for legal over a hosted endpoint. 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 Processos TRT (Justiça do Trabalho) when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
trt_processos_consultar, show_version, report_bug.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 68/100 · Great | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| 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 | 202 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 6 | 7 |
| Full listing | View Melta UI | View Processos TRT (Justiça do Trabalho) |
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.
Processos TRT (Justiça do Trabalho) tools 7
trt_processos_consultarConsulta processos de uma pessoa ou empresa no Tribunal Regional do Trabalho (TRT) a partir do CPF ou CNPJ e região. Hospedado pela plataforma, sem credenciais, pague por consulta com crédito pré-pago. Consulta informação de ACESSO PÚBLICO em bases e fontes oficiais (a mesma disponível ao cidadão), não é dado privado nem sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).show_versionShow the current MCP platform and adapter versions.report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
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"
]
}
}
}
Processos TRT (Justiça do Trabalho)
{
"mcpServers": {
"processos-trt-justi-a-do-trabalho": {
"url": "https://api.mcp.ai/p_trt_processos"
}
}
}
Frequently asked questions
Melta UI is categorized under Legal and uses a local stdio subprocess. Processos TRT (Justiça do Trabalho) belongs to Legal and uses a remote HTTP/SSE transport. Pick Melta UI for legal work and Processos TRT (Justiça do Trabalho) 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.
Melta UI has no declared pricing — check the project's own site. Processos TRT (Justiça do Trabalho) 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 melta-ui and processos-trt-justi-a-do-trabalho 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. Processos TRT (Justiça do Trabalho) has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.