LegalOne

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

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

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

    How to connect

    How to connect LegalOne to Claude

    The server address to paste into Claude settings:

    https://api.mcp.ai/p_legalone

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect LegalOne to ChatGPT

    The server address to paste into ChatGPT settings:

    https://api.mcp.ai/p_legalone

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect LegalOne to Cursor

    The server address to paste into Cursor settings:

    https://api.mcp.ai/p_legalone

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (45)

    Raw names from tools/list. Only developers need these.

    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 support: accepts ids for batched execution.
    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.
    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 é escopo fora do contrato do escritório, não credencial errada).
    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.
    legalone_list_litigationsLista Processos/litígios, visão consolidada do contencioso (OData /Litigations). Filtre com $filter/$top/$skip/$orderby/$expand.
    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.
    legalone_create_litigationsCria um(a) Processos/litígios, visão consolidada do contencioso (OData POST /Litigations). `data` = corpo da entidade conforme a API oficial.
    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.
    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.
    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.
    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.
    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.
    legalone_list_contactsLista Contatos (pessoas físicas/jurídicas: clientes, partes, advogados) (OData /Contacts). Filtre com $filter/$top/$skip/$orderby/$expand.
    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.
    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.
    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.
    legalone_list_appointmentsLista Compromissos/agenda (OData /Appointments). Filtre com $filter/$top/$skip/$orderby/$expand.
    legalone_get_appointmentsBusca um(a) Compromissos/agenda por id (OData /Appointments/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.
    legalone_create_appointmentsCria um(a) Compromissos/agenda (OData POST /Appointments). `data` = corpo da entidade conforme a API oficial.
    legalone_update_appointmentsAtualiza um(a) Compromissos/agenda (OData PATCH /Appointments/{id}). `data` = campos a alterar. Bulk support: accepts ids for batched execution.
    legalone_list_tasksLista Tarefas/providências (o prazo vem no campo deadLine) (OData /Tasks). Filtre com $filter/$top/$skip/$orderby/$expand.
    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.
    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.
    legalone_update_tasksAtualiza 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.
    legalone_list_appointmentstasksLista Agenda unificada: compromissos e tarefas na mesma lista (OData /AppointmentsTasks). Filtre com $filter/$top/$skip/$orderby/$expand.
    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.
    legalone_list_updatesLista Andamentos/publicações/atualizações do processo (OData /Updates). Filtre com $filter/$top/$skip/$orderby/$expand.
    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.
    legalone_create_updatesCria um(a) Andamentos/publicações/atualizações do processo (OData POST /Updates). `data` = corpo da entidade conforme a API oficial.
    legalone_list_documentsLista Documentos (GED) (OData /Documents). Filtre com $filter/$top/$skip/$orderby/$expand.
    legalone_get_documentsBusca um(a) Documentos (GED) por id (OData /Documents/{id}). Use $expand para sub-recursos. Bulk support: accepts ids for batched execution.
    legalone_list_areasLista Áreas de atuação (OData /Areas). Filtre com $filter/$top/$skip/$orderby/$expand.
    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.
    legalone_list_servicetypesLista Tipos de serviço/processo (OData /ServiceTypes). Filtre com $filter/$top/$skip/$orderby/$expand.
    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.
    legalone_list_usersLista Usuários/responsáveis do escritório (OData /Users). Filtre com $filter/$top/$skip/$orderby/$expand.
    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.
    legalone_list_customfielddefinitionsLista Definições de campos personalizados (OData /CustomFieldsDefinitions). Filtre com $filter/$top/$skip/$orderby/$expand.
    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.
    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.