Index / MCP servers / LegalOne

LegalOne MCP server

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.

Status
Answering
Tools
45
Reliability
6 of 6 checks
Response time
685 ms
Transport
streamable HTTP
Last checked
22 October 2026

Wrapper for the official LegalOne API (Thomson Reuters / Novajus, Premium package): lawsuits and lit

Description as the publisher wrote it.

The 45 tools LegalOne offers

ToolWhat it does
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-on
Inputs: token
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.
legalone_create_appointmentsCria um(a) Compromissos/agenda (OData POST /Appointments). `data` = corpo da entidade conforme a API oficial.
Inputs: data
legalone_create_contactsCria 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_lawsuitsCria 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_litigationsCria 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_tasksCria 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_updatesCria um(a) Andamentos/publicações/atualizações do processo (OData POST /Updates). `data` = corpo da entidade conforme a API oficial.
Inputs: data
legalone_customfield_optionsOpçõ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_appointmentsBusca 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_appointmentstasksBusca 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_areasBusca 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_contactsBusca 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_customfielddefinitionsBusca 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_documentsBusca 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_lawsuitsBusca 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_litigationsBusca 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_servicetypesBusca 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_tasksBusca 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_updatesBusca 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_usersBusca 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_appointmentsLista Compromissos/agenda (OData /Appointments). Filtre com $filter/$top/$skip/$orderby/$expand.
Inputs: $filter, $expand, $select, $orderby, $top, $skip
legalone_list_appointmentstasksLista 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_areasLista Áreas de atuação (OData /Areas). Filtre com $filter/$top/$skip/$orderby/$expand.
Inputs: $filter, $expand, $select, $orderby, $top, $skip
legalone_list_contactsLista 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_customfielddefinitionsLista Definições de campos personalizados (OData /CustomFieldsDefinitions). Filtre com $filter/$top/$skip/$orderby/$expand.
Inputs: $filter, $expand, $select, $orderby, $top, $skip
legalone_list_documentsLista Documentos (GED) (OData /Documents). Filtre com $filter/$top/$skip/$orderby/$expand.
Inputs: $filter, $expand, $select, $orderby, $top, $skip
legalone_list_lawsuitsLista 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_litigationsLista 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_servicetypesLista Tipos de serviço/processo (OData /ServiceTypes). Filtre com $filter/$top/$skip/$orderby/$expand.
Inputs: $filter, $expand, $select, $orderby, $top, $skip
legalone_list_tasksLista 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_updatesLista 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_usersLista Usuários/responsáveis do escritório (OData /Users). Filtre com $filter/$top/$skip/$orderby/$expand.
Inputs: $filter, $expand, $select, $orderby, $top, $skip
legalone_metadataMetadados 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_getGET 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_requestEscape 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_appointmentsAtualiza 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_contactsAtualiza 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_lawsuitsAtualiza 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_litigationsAtualiza 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
5 more tools

legalone_update_tasks, marketplace, report_bug, show_version, toolkit_info

Add LegalOne to your AI client

Every block below points at https://api.mcp.ai/p_legalone. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http legalone https://api.mcp.ai/p_legalone
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "legalone": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.mcp.ai/p_legalone"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "legalone": {
      "url": "https://api.mcp.ai/p_legalone"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "legalone": {
      "type": "http",
      "url": "https://api.mcp.ai/p_legalone"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "legalone": {
      "url": "https://api.mcp.ai/p_legalone"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "legalone": {
      "serverUrl": "https://api.mcp.ai/p_legalone"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "legalone": {
      "url": "https://api.mcp.ai/p_legalone"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: LegalOne
version: 0.0.1
schema: v1
mcpServers:
  - name: LegalOne
    type: streamable-http
    url: https://api.mcp.ai/p_legalone
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "legalone": {
      "httpUrl": "https://api.mcp.ai/p_legalone"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "legalone": {
      "type": "http",
      "url": "https://api.mcp.ai/p_legalone"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "legalone": {
      "url": "https://api.mcp.ai/p_legalone"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fapi.mcp.ai%2Fp_legalone&type=streamable_http&id=legalone&name=LegalOne

Is LegalOne up right now?

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.

MCP servers similar to LegalOne

Questions about LegalOne

How many tools does LegalOne have?

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.

Is LegalOne down?

It answered our last check on 22 October 2026 in 685 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add LegalOne to Cursor?

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.

Does LegalOne need an API key?

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.

Where this comes from

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.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.