LegalOne is a remote MCP server that gives an AI agent 45 tools, among them authenticate, connect, legalone_create_appointments. It answers at https://api.mcp.ai/p_legalone over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
Wrapper for the official LegalOne API (Thomson Reuters / Novajus, Premium package): lawsuits and lit
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
authenticate | 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-on Inputs: token |
connect | 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_appointments | Cria um(a) Compromissos/agenda (OData POST /Appointments). `data` = corpo da entidade conforme a API oficial. Inputs: data |
legalone_create_contacts | Cria um(a) Contatos (pessoas físicas/jurídicas: clientes, partes, advogados) (OData POST /Contacts). `data` = corpo da entidade conforme a API oficial. Inputs: data |
legalone_create_lawsuits | 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. Inputs: data |
legalone_create_litigations | Cria um(a) Processos/litígios, visão consolidada do contencioso (OData POST /Litigations). `data` = corpo da entidade conforme a API oficial. Inputs: data |
legalone_create_tasks | Cria um(a) Tarefas/providências (o prazo vem no campo deadLine) (OData POST /Tasks). `data` = corpo da entidade conforme a API oficial. Inputs: data |
legalone_create_updates | Cria um(a) Andamentos/publicações/atualizações do processo (OData POST /Updates). `data` = corpo da entidade conforme a API oficial. Inputs: data |
legalone_customfield_options | 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. Inputs: id, ids |
legalone_get_appointments | Busca um(a) Compromissos/agenda por id (OData /Appointments/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution. Inputs: id, $expand, $select, query, ids |
legalone_get_appointmentstasks | 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. Inputs: id, $expand, $select, query, ids |
legalone_get_areas | Busca um(a) Áreas de atuação por id (OData /Areas/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution. Inputs: id, $expand, $select, query, ids |
legalone_get_contacts | 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. Inputs: id, $expand, $select, query, ids |
legalone_get_customfielddefinitions | 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. Inputs: id, $expand, $select, query, ids |
legalone_get_documents | Busca um(a) Documentos (GED) por id (OData /Documents/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution. Inputs: id, $expand, $select, query, ids |
legalone_get_lawsuits | 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. Inputs: id, $expand, $select, query, ids |
legalone_get_litigations | 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. Inputs: id, $expand, $select, query, ids |
legalone_get_servicetypes | 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. Inputs: id, $expand, $select, query, ids |
legalone_get_tasks | 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. Inputs: id, $expand, $select, query, ids |
legalone_get_updates | 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. Inputs: id, $expand, $select, query, ids |
legalone_get_users | 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. Inputs: id, $expand, $select, query, ids |
legalone_list_appointments | Lista Compromissos/agenda (OData /Appointments). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_appointmentstasks | Lista Agenda unificada: compromissos e tarefas na mesma lista (OData /AppointmentsTasks). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_areas | Lista Áreas de atuação (OData /Areas). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_contacts | Lista Contatos (pessoas físicas/jurídicas: clientes, partes, advogados) (OData /Contacts). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_customfielddefinitions | Lista Definições de campos personalizados (OData /CustomFieldsDefinitions). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_documents | Lista Documentos (GED) (OData /Documents). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_lawsuits | 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. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_litigations | Lista Processos/litígios, visão consolidada do contencioso (OData /Litigations). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_servicetypes | Lista Tipos de serviço/processo (OData /ServiceTypes). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_tasks | Lista Tarefas/providências (o prazo vem no campo deadLine) (OData /Tasks). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_updates | Lista Andamentos/publicações/atualizações do processo (OData /Updates). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_list_users | Lista Usuários/responsáveis do escritório (OData /Users). Filtre com $filter/$top/$skip/$orderby/$expand. Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_metadata | 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 é es |
legalone_odata_get | 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 sup Inputs: $filter, $expand, $select, $orderby, $top, $skip |
legalone_request | 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. Inputs: method, path, query, body |
legalone_update_appointments | Atualiza um(a) Compromissos/agenda (OData PATCH /Appointments/{id}). `data` = campos a alterar. Bulk support: accepts ids for batched execution. Inputs: id, data, ids |
legalone_update_contacts | 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. Inputs: id, data, ids |
legalone_update_lawsuits | 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. Inputs: id, data, ids |
legalone_update_litigations | 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. Inputs: id, data, ids |
legalone_update_tasks, marketplace, report_bug, show_version, toolkit_info
Every block below points at https://api.mcp.ai/p_legalone. Pick your client and copy.
claude mcp add --transport http legalone https://api.mcp.ai/p_legalone
{
"mcpServers": {
"legalone": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.mcp.ai/p_legalone"]
}
}
}{
"mcpServers": {
"legalone": {
"url": "https://api.mcp.ai/p_legalone"
}
}
}{
"servers": {
"legalone": {
"type": "http",
"url": "https://api.mcp.ai/p_legalone"
}
}
}{
"context_servers": {
"legalone": {
"url": "https://api.mcp.ai/p_legalone"
}
}
}{
"mcpServers": {
"legalone": {
"serverUrl": "https://api.mcp.ai/p_legalone"
}
}
}{
"mcpServers": {
"legalone": {
"url": "https://api.mcp.ai/p_legalone"
}
}
}name: LegalOne
version: 0.0.1
schema: v1
mcpServers:
- name: LegalOne
type: streamable-http
url: https://api.mcp.ai/p_legalone{
"mcpServers": {
"legalone": {
"httpUrl": "https://api.mcp.ai/p_legalone"
}
}
}{
"mcpServers": {
"legalone": {
"type": "http",
"url": "https://api.mcp.ai/p_legalone"
}
}
}{
"mcpServers": {
"legalone": {
"url": "https://api.mcp.ai/p_legalone"
}
}
}goose://extension?url=https%3A%2F%2Fapi.mcp.ai%2Fp_legalone&type=streamable_http&id=legalone&name=LegalOne
It answered our last check on 22 October 2026 in 685 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
45, as returned by the server's own tools/list on 15 September 2026: authenticate, connect, legalone_create_appointments, legalone_create_contacts, legalone_create_lawsuits, legalone_create_litigations, legalone_create_tasks, legalone_create_updates, and 37 more.
It answered our last check on 22 October 2026 in 685 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.mcp.ai/p_legalone. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.mcp-dir. Endpoint host: api.mcp.ai. ARD identifier: urn:air:io.github.mcp-dir:mcp:legalone-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.