LegalOne MCP server

• authenticateFree

  MCP.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.

• connectFree

  Returns 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.

• legalone_create_appointmentswrite actionFree

  Cria um(a) Compromissos/agenda (OData POST /Appointments). `data` = corpo da entidade conforme a API oficial.

• legalone_create_contactswrite actionFree

  Cria um(a) Contatos (pessoas físicas/jurídicas: clientes, partes, advogados) (OData POST /Contacts). `data` = corpo da entidade conforme a API oficial.

• legalone_create_lawsuitswrite actionFree

  Cria um(a) Processos judiciais com os campos próprios do módulo (valor da causa, partes, pedidos) (OData POST /Lawsuits). `data` = corpo da entidade conforme a API oficial.

• legalone_create_litigationswrite actionFree

  Cria um(a) Processos/litígios, visão consolidada do contencioso (OData POST /Litigations). `data` = corpo da entidade conforme a API oficial.

• legalone_create_taskswrite actionFree

  Cria um(a) Tarefas/providências (o prazo vem no campo deadLine) (OData POST /Tasks). `data` = corpo da entidade conforme a API oficial.

• legalone_create_updateswrite actionFree

  Cria um(a) Andamentos/publicações/atualizações do processo (OData POST /Updates). `data` = corpo da entidade conforme a API oficial.

• legalone_customfield_optionsFree

  Opções de um campo personalizado (/CustomFieldsDefinitions/{id}/options), resolve o texto por trás dos valores listItemId que aparecem em customFields. Bulk support: accepts ids for batched execution.

• legalone_get_appointmentsFree

  Busca um(a) Compromissos/agenda por id (OData /Appointments/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_appointmentstasksFree

  Busca um(a) Agenda unificada: compromissos e tarefas na mesma lista por id (OData /AppointmentsTasks/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_areasFree

  Busca um(a) Áreas de atuação por id (OData /Areas/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_contactsFree

  Busca um(a) Contatos (pessoas físicas/jurídicas: clientes, partes, advogados) por id (OData /Contacts/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_customfielddefinitionsFree

  Busca um(a) Definições de campos personalizados por id (OData /CustomFieldsDefinitions/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_documentsFree

  Busca um(a) Documentos (GED) por id (OData /Documents/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_lawsuitsFree

  Busca um(a) Processos judiciais com os campos próprios do módulo (valor da causa, partes, pedidos) por id (OData /Lawsuits/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_litigationsFree

  Busca um(a) Processos/litígios, visão consolidada do contencioso por id (OData /Litigations/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_servicetypesFree

  Busca um(a) Tipos de serviço/processo por id (OData /ServiceTypes/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_tasksFree

  Busca um(a) Tarefas/providências (o prazo vem no campo deadLine) por id (OData /Tasks/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_updatesFree

  Busca um(a) Andamentos/publicações/atualizações do processo por id (OData /Updates/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_get_usersFree

  Busca um(a) Usuários/responsáveis do escritório por id (OData /Users/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.

• legalone_list_appointmentsFree

  Lista Compromissos/agenda (OData /Appointments). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_appointmentstasksFree

  Lista Agenda unificada: compromissos e tarefas na mesma lista (OData /AppointmentsTasks). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_areasFree

  Lista Áreas de atuação (OData /Areas). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_contactsFree

  Lista Contatos (pessoas físicas/jurídicas: clientes, partes, advogados) (OData /Contacts). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_customfielddefinitionsFree

  Lista Definições de campos personalizados (OData /CustomFieldsDefinitions). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_documentsFree

  Lista Documentos (GED) (OData /Documents). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_lawsuitsFree

  Lista Processos judiciais com os campos próprios do módulo (valor da causa, partes, pedidos) (OData /Lawsuits). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_litigationsFree

  Lista Processos/litígios, visão consolidada do contencioso (OData /Litigations). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_servicetypesFree

  Lista Tipos de serviço/processo (OData /ServiceTypes). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_tasksFree

  Lista Tarefas/providências (o prazo vem no campo deadLine) (OData /Tasks). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_updatesFree

  Lista Andamentos/publicações/atualizações do processo (OData /Updates). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_list_usersFree

  Lista Usuários/responsáveis do escritório (OData /Users). Filtre com $filter/$top/$skip/$orderby/$expand.

• legalone_metadataFree

  Metadados da conexão: escopos que a Thomson Reuters liberou para este escritório, produtos da API, base da API e as coleções disponíveis com as tools de cada uma. Chame antes de montar uma consulta, e depois de um 403 (403 quase sempre é escopo fora do contrato do escritório, não credencial errada).

• legalone_odata_getFree

  GET genérico em qualquer coleção/recurso OData do LegalOne. Informe `entity` (ex.: "Litigations") e opcionalmente `id`; suporta $filter/$expand/$select/$top/$skip/$orderby. Use isto para entidades não cobertas por uma tool nomeada. Bulk support: accepts ids for batched execution.

• legalone_requestFree

  Escape hatch: chamada OData crua. `method` (GET/POST/PATCH/PUT/DELETE) + `path` (ex.: "/Litigations/2479") + `query`/`body` opcionais. Cobre endpoints/ações fora das tools nomeadas.

• legalone_update_appointmentswrite actionFree

  Atualiza um(a) Compromissos/agenda (OData PATCH /Appointments/{id}). `data` = campos a alterar. Bulk support: accepts ids for batched execution.

• legalone_update_contactswrite actionFree

  Atualiza um(a) Contatos (pessoas físicas/jurídicas: clientes, partes, advogados) (OData PATCH /Contacts/{id}). `data` = campos a alterar. Bulk support: accepts ids for batched execution.

• legalone_update_lawsuitswrite actionFree

  Atualiza um(a) Processos judiciais com os campos próprios do módulo (valor da causa, partes, pedidos) (OData PATCH /Lawsuits/{id}). `data` = campos a alterar. Bulk support: accepts ids for batched execution.

• legalone_update_litigationswrite actionFree

  Atualiza um(a) Processos/litígios, visão consolidada do contencioso (OData PATCH /Litigations/{id}). `data` = campos a alterar. Bulk support: accepts ids for batched execution.

• legalone_update_taskswrite actionFree

  Atualiza um(a) Tarefas/providências (o prazo vem no campo deadLine) (OData PATCH /Tasks/{id}). `data` = campos a alterar. Bulk support: accepts ids for batched execution.

• marketplaceFree

  The 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.

• report_bugFree

  Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

• show_versionFree

  Show the current MCP platform and adapter versions.

• toolkit_infoFree

  Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 2058ms17/20
• Tool poisoning45 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 11 write-action tools with no auth3/15
• Maintenancelast push 63 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Safety score

75/100

higher than 45% of 48,255 servers

Tools

45

the typical server has 7

Tools that change things

24%

typical: 0%. Fewer write tools means less an agent can break

Uptime

96%

of our recent checks; the typical remote server answers 100%

Response time

167 ms

faster than 70% of 30,031 servers

GitHub stars

1

more than 65% of 28,688 servers

LegalOne: common questions

Is LegalOne MCP server safe?

Mostly: it is graded B (75/100). Read the LegalOne safety report

How do I install LegalOne?

It runs remotely at api.mcp.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does LegalOne need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is LegalOne maintained?

The last commit was 66 days ago (2026-08-30). The latest release is v0.1.0.

Is LegalOne up?

96% of our last 28 checks got an answer. We check remote servers about four times a day.

How does LegalOne compare with other MCP servers?

safety score 75/100 (higher than 45% of 48,255 servers); tools 45 (the typical server has 7); tools that change things 24% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.