Processos TRT (Justiça do Trabalho) vs Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT)
A side-by-side look at the Processos TRT (Justiça do Trabalho) and Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Processos TRT (Justiça do Trabalho) for legal work over a hosted endpoint; choose Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) 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 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.
Choose Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
tribunal_trt8_ceat_consultar, show_version, report_bug.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 55/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 7 | 7 |
| Full listing | View Processos TRT (Justiça do Trabalho) | View Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) |
Tools & capabilities
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.
Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) tools 7
tribunal_trt8_ceat_consultarTribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT), consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado 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.
Processos TRT (Justiça do Trabalho)
{
"mcpServers": {
"processos-trt-justi-a-do-trabalho": {
"url": "https://api.mcp.ai/p_trt_processos"
}
}
}
Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT)
{
"mcpServers": {
"tribunal-trt8-certid-o-eletr-nica-de-a-es-trabalhistas-ceat": {
"url": "https://api.mcp.ai/p_tribunal_trt8_ceat"
}
}
}
Frequently asked questions
Processos TRT (Justiça do Trabalho) is categorized under Legal and uses a remote HTTP/SSE transport. Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) belongs to Legal and uses a remote HTTP/SSE transport. Pick Processos TRT (Justiça do Trabalho) for legal work and Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) 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.
Processos TRT (Justiça do Trabalho) has no declared pricing — check the project's own site. Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) 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 processos-trt-justi-a-do-trabalho and tribunal-trt8-certid-o-eletr-nica-de-a-es-trabalhistas-ceat as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Processos TRT (Justiça do Trabalho) has a quality signal of 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) has 55/100 (Good) with 3 views, 0 installs and 0 GitHub stars.
Related comparisons
Popular comparisons with Processos TRT (Justiça do Trabalho)
Popular comparisons with Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT)
Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) vs Kentucky Code
Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) vs Melta UI
Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) vs LienDeadline
Tribunal TRT8: Certidão Eletrônica de Ações Trabalhistas (CEAT) vs Ris