Black Friday: 30% off any plan for 12 months with the code BF2026, until 30 November. See the plans

Legalnaut

DOCUMENTATION · MCP SERVER

Connect your AI assistant to Legalnaut

Legalnaut runs a remote MCP server. Any assistant that supports MCP can search and read the case files you can open, run ready-made workflows on a matter and, if you allow it, add documents and record your decisions.

Server address

https://legalnaut.com/mcp

Transport: Streamable HTTP. Authorization: OAuth 2.1 with PKCE; clients identify themselves by a Client ID Metadata Document or register dynamically; personal keys as a bearer token.

Quick start

  1. 1 Copy the server address: https://legalnaut.com/mcp
  2. 2 In your assistant, add a custom connector or remote MCP server and paste the address. Leave any client ID or secret empty.
  3. 3 Your browser opens Legalnaut. Sign in, choose "Read only" or "Read and change", and select Connect.
  4. 4 Ask about a matter, or pick a Legalnaut workflow from the assistant's prompt menu. Start with "List my Legalnaut matters".

Signing in

OAuth (recommended)

  • The assistant finds Legalnaut's sign-in on its own: the server answers an unauthenticated request with a pointer to its OAuth metadata. The assistant then identifies itself by its Client ID Metadata Document (a URL on its own domain, so the name on the consent screen is verified) or, if it does not support that, registers itself.
  • You sign in with your usual Legalnaut login, including two-factor authentication or a passkey.
  • On the consent screen you choose what the assistant may do. Read only is preselected.
  • Access tokens last an hour and renew themselves; a connection asks you to sign in again after 90 days.

Personal key

For clients without OAuth, create a key under Settings → AI assistants. It starts with ln_mcp_ and is sent as "Authorization: Bearer <key>". It is shown once; store it like a password and disconnect it when you stop using it.

Open Settings → AI assistants →

Access levels

Read only

Every read tool and the read-only workflows. Tools that change a matter are hidden and refused.

Read and change

Also adding documents, filing into dossiers, team notes and contradiction review.

The level is a ceiling on top of your role. In each matter the assistant can do no more than you can in the app: a viewer cannot change anything, and documents marked sensitive or hidden from you stay out of reach.

Configuration with a key (JSON used by most clients):

Configuration
{
    "mcpServers": {
        "legalnaut": {
            "url": "https://legalnaut.com/mcp",
            "headers": {
                "Authorization": "Bearer ln_mcp_…"
            }
        }
    }
}

Setting up your client

Pick your assistant. Where a client can add a custom connector depends on its vendor and your plan with it; the vendor's own guide is linked under each section.

Pick your assistant

Claude

Sign-in: OAuth Vendor guide ↗
  1. 1 In Claude (claude.ai or the desktop app), open Customize → Connectors and choose Add custom connector.
  2. 2 Name it Legalnaut and paste https://legalnaut.com/mcp as the URL. Keep the default sign-in.
  3. 3 Select Connect, sign in to Legalnaut in the window that opens and approve.
  4. 4 In a chat, open the + menu to switch the connector on and to find the Legalnaut workflows.

A connector added on claude.ai also works in the Claude desktop and mobile apps. On Team and Enterprise plans an owner may have to add it for the organisation first.

ChatGPT

Sign-in: OAuth Vendor guide ↗
  1. 1 In ChatGPT on the web, open Settings → Apps & Connectors. If custom connectors are off, switch on developer mode under Advanced settings (on business plans an admin may have to allow it).
  2. 2 Choose Create (or Add custom MCP server), name it Legalnaut and paste https://legalnaut.com/mcp. Choose OAuth as the authentication.
  3. 3 Sign in to Legalnaut when ChatGPT asks, and approve.
  4. 4 In a chat, add Legalnaut from the + menu before you ask.

ChatGPT does not accept personal keys; it signs in with OAuth only.

Claude Code

Sign-in: OAuth Vendor guide ↗
  1. 1 Run the command below in a terminal.
  2. 2 Start Claude Code, type /mcp, choose legalnaut and sign in to Legalnaut in the browser.
Terminal
claude mcp add --transport http legalnaut https://legalnaut.com/mcp
With a personal key instead
claude mcp add --transport http legalnaut https://legalnaut.com/mcp --header "Authorization: Bearer <key>"
C

Cursor

Sign-in: OAuth Vendor guide ↗
  1. 1 Use the Add to Cursor button under Settings → AI assistants, or add the server to ~/.cursor/mcp.json as below.
  2. 2 Open Cursor Settings → MCP and select Connect next to legalnaut to sign in.
One-click install: Cursor
Configuration
{
    "mcpServers": {
        "legalnaut": {
            "url": "https://legalnaut.com/mcp"
        }
    }
}

VS Code · GitHub Copilot

Sign-in: OAuth Vendor guide ↗
  1. 1 Use the Add to VS Code button under Settings → AI assistants, or run "MCP: Add Server" from the command palette, choose HTTP and paste https://legalnaut.com/mcp.
  2. 2 Start the server from the MCP view and sign in when VS Code asks. Use it from Copilot Chat in agent mode.
One-click install: VS Code
Configuration
{
    "servers": {
        "legalnaut": {
            "type": "http",
            "url": "https://legalnaut.com/mcp"
        }
    }
}

Windsurf

Sign-in: OAuth Vendor guide ↗
  1. 1 Open Windsurf Settings → Cascade → MCP servers and choose to add a server (or edit mcp_config.json).
  2. 2 Add the server as below and sign in when Windsurf asks. If your version cannot sign in to remote servers, use a personal key in a header.
Configuration
{
    "mcpServers": {
        "legalnaut": {
            "serverUrl": "https://legalnaut.com/mcp"
        }
    }
}

Zed

Sign-in: OAuth Vendor guide ↗
  1. 1 Open the Agent panel settings, choose Add Custom Server and enter https://legalnaut.com/mcp (or add it to settings.json under context_servers).
  2. 2 Zed opens the Legalnaut sign-in on first use.
Configuration
{
    "context_servers": {
        "legalnaut": {
            "url": "https://legalnaut.com/mcp"
        }
    }
}

Gemini CLI

Sign-in: OAuth Vendor guide ↗
  1. 1 Add the server to ~/.gemini/settings.json as below.
  2. 2 In Gemini CLI, run /mcp auth legalnaut and sign in to Legalnaut in the browser.
Configuration
{
    "mcpServers": {
        "legalnaut": {
            "httpUrl": "https://legalnaut.com/mcp"
        }
    }
}
MC

Microsoft Copilot Studio

Sign-in: OAuth Vendor guide ↗
  1. 1 In your agent, open Tools → Add a tool → New tool → Model Context Protocol.
  2. 2 Enter Legalnaut as the name and https://legalnaut.com/mcp as the server URL, and choose OAuth 2.0 with dynamic discovery.
  3. 3 Create a connection and sign in to Legalnaut.

Each person who uses the agent signs in with their own Legalnaut account, so each sees only their own matters.

Mistral Le Chat

Sign-in: OAuth Vendor guide ↗
  1. 1 In Le Chat, open Intelligence → Connectors and add a custom MCP connector (an admin may have to do this for the organisation).
  2. 2 Paste https://legalnaut.com/mcp; Le Chat detects OAuth. Sign in to Legalnaut and approve.

Perplexity

Sign-in: OAuth Vendor guide ↗
  1. 1 In Perplexity, open Settings → Connectors and add a custom remote connector.
  2. 2 Paste https://legalnaut.com/mcp, choose OAuth, and sign in to Legalnaut.
LS

LM Studio

Sign-in: OAuth Vendor guide ↗
  1. 1 Open the Program tab → Install → Edit mcp.json and add the server as below.
  2. 2 LM Studio opens the Legalnaut sign-in when a model first calls a tool.
Configuration
{
    "mcpServers": {
        "legalnaut": {
            "url": "https://legalnaut.com/mcp"
        }
    }
}

Raycast

Sign-in: OAuth Vendor guide ↗
  1. 1 Run the Install Server command, choose HTTP and paste https://legalnaut.com/mcp.
  2. 2 Raycast signs in to Legalnaut the first time you mention @legalnaut in AI Chat.
GX

Grok (xAI API)

Sign-in: Key Vendor guide ↗
  1. 1 The Grok apps cannot add a custom MCP server yet. Through the xAI API, pass Legalnaut as a remote MCP tool with a personal key, as below.
Configuration
{
    "type": "mcp",
    "server_url": "https://legalnaut.com/mcp",
    "server_label": "legalnaut",
    "authorization": "<your ln_mcp_ key>"
}

Any MCP client

Sign-in: OAuth or key Vendor guide ↗
  1. 1 Any client that supports remote MCP servers over Streamable HTTP can connect to the server address.
  2. 2 If it supports OAuth (a client metadata document or dynamic registration), it signs in on its own. Otherwise send a personal key as "Authorization: Bearer <key>".
  3. 3 For a client that only runs local servers, use the mcp-remote bridge below.
Terminal
npx mcp-remote https://legalnaut.com/mcp

Tools

Every tool except list_matters takes an optional `matter`: the key list_matters returns. Without it the tool works on the matter you have open in Legalnaut. Ids of documents, claims and events are those the other tools return.

Read: every connection · 22

  • list_matters
    List matters. The matters (case files) this user can open in Legalnaut, with each matter's key (the `matter` argument of the other tools), the user's role in each, and which one is open in the app now.
  • get_matter_overview
    Get a matter overview. Counts for the matter: documents, claims and events, claims by kind, the most frequent speakers and documents by category.
  • list_documents
    List documents. The documents of the matter as a list, page by page: id, title, date, sender, category, relevance and page count.
  • search_documents
    Search documents. Full-text search over the matter's case file (mails and filed documents). Returns documents with id, title, date, sender and summary. Matches exact words, names or phrases.
  • semantic_search
    Search by meaning. Semantic search: finds documents whose meaning matches a sentence, even without the same words and across languages. The query is a full sentence describing the situation or topic.
  • read_document
    Read a document. Read one document of the case file by id: its text, claims, people and summary. Long texts are returned in windows; a truncated answer carries next_offset for the next window. A line [[p.N]] marks where page N starts.
  • get_mail_thread
    Get a mail thread. Every message of the mail thread a mail belongs to, in order, with summaries. The full body of each message is available by its document id.
  • search_attachments
    Search attachments. Full-text search over the extracted text of attachments (scans, photos, recordings).
  • read_attachment
    Read an attachment. The full extracted text of one attachment by id (OCR or transcript). Long texts are returned in windows (offset).
  • search_new_uploads
    Search new uploads. Full-text search over documents the team uploaded that are still being analysed and not yet filed into the case file.
  • read_new_upload
    Read a new upload. The full text of a document still being analysed (by the upload_id search_new_uploads returned). Long texts are returned in windows (offset).
  • get_timeline
    Get the timeline. Events on the matter's timeline, filtered by date range, jurisdiction or the people involved, each with its source document.
  • search_events
    Search events. Timeline events whose description mentions a word or phrase; no date range needed.
  • search_claims
    Search claims. Statements made in the case file, by speaker, kind (accusation, admission, denial, threat, promise…) or topic, each with its document and page.
  • get_person
    Get a person or organisation. The profile of a person, organisation or place: aliases, role, what they said, what others said about them and the documents they wrote. Looked up by id or by name.
  • get_contradictions
    Get contradictions. Claim-to-document relations: contradicts, confirms, contextualizes. Each carries review_status: 'confirmed' means a lawyer verified it; 'suggested' is an unverified AI finding.
  • get_amounts
    Get sums of money. Sums of money named in the documents (payments, wages, invoices, claimed and awarded sums), each with payer, payee, date, status and source page, plus totals the application computed.
  • list_by_legal_provision
    List evidence by legal provision. Documents and claims tagged with a legal provision. The tags are AI hypotheses that a lawyer still has to review.
  • get_dossiers
    Get dossiers. The dossiers (working collections inside the matter), or one dossier with its items, exhibit numbers and notes.
  • get_proof_chart
    Get a proof chart. The proof chart of one dossier: each issue to prove, who bears the burden, the evidence for and against it, the gaps with no supporting document, and AI suggestions still awaiting a lawyer.
  • get_deadlines
    Get deadlines. Deadlines, hearings and meetings of the matter from today on (or the past ones), with kind, date and time in the matter's time zone, location, notes and the document each one comes from.
  • get_import_status
    Get import status. The state of one import (by the import_id add_document returned) or of the matter's latest imports: queued, analysing, completed or failed, files done, files waiting for pages, and the pages left this month.

Change: read-and-change connections only · 5

  • add_document
    Add a document. Add one document to the matter: either `text` (a pasted e-mail, meeting notes, a transcript) or a small file as `content_base64` (up to 10 MB; PDF, Word, e-mail, image, audio). Legalnaut reads, dates and cross-checks it in the background, as an import from the app, and pages are counted as usual. ZIP archives, mailbox exports and large scans go through create_upload_link instead.
  • create_upload_link
    Create an upload link. A one-time link (valid 30 minutes) that opens this matter's Import screen in Legalnaut, for ZIP archives, mailbox exports (.mbox, .pst, .eml) and large scans. Only the user it was created for can use it, signed in to their own account.
  • add_to_dossier
    Add to a dossier. File a document, claim, event or contradiction into a dossier (ids as listed by get_dossiers), optionally with a note on why it belongs there and the lawyer's reading of it: significance (key, relevant, background), stance (favourable, adverse, neutral) and whether it is disputed. Adding an item already in the dossier only updates the reading.
  • add_note
    Add a note. Leave a note for the team on a document, claim, event or contradiction. It is saved in the user's name and marked as written with an AI assistant.
  • review_contradiction
    Review a contradiction. Record the user's verdict on a contradiction or confirmation found by Legalnaut (ids as listed by get_contradictions): confirm it, dismiss it, or reopen it as a suggestion. The user is recorded as the reviewer.

Prompts (workflows)

Prompts appear in your assistant's prompt menu. Each runs a workflow on one matter with the tools above; arguments in brackets are optional.

summarise_matter

Summarise the matter

A briefing on the whole matter: what it is about, the parties, the key events in order, where the accounts disagree, what is still missing and what comes next.

matter?
topic_chronology

Chronology of a topic

Everything the case file says about one topic, person or thing, in date order, each entry with its document and page.

matter? topic
prepare_witness

Prepare a witness examination

A dossier on one person (what they said, what others said about them, where the record contradicts them) and an examination outline built from it.

matter? person
review_new_contradictions

Review new contradictions

Goes through the contradictions still awaiting a lawyer, one by one, with both quotations, so the user can confirm or dismiss each.

matter? limit?
proof_gaps

What the proof chart is missing

For one dossier, the issues with no supporting evidence yet and where in the case file evidence for them might be.

matter? dossier?
deadlines_next_30_days

Deadlines in the next 30 days

The matter's deadlines and hearings in the coming days, each with what it requires and the documents behind it.

matter? days?
whats_new_this_week

What is new this week

What entered the matter recently: new documents, what they say, new contradictions and deadlines.

matter? days?
file_documents_from_chat

Add documents from this chat

Adds the documents, e-mails or notes from this conversation to the matter, then checks they were filed.

matter? what?

Things to ask

List my Legalnaut matters and summarise the one called Delivery dispute.
What did the site manager say about the damaged boxes? Quote the pages.
Which contradictions are still waiting for review in this matter?
Build a chronology of the payments between the parties in 2024.
Which issues in the proof chart have no supporting document yet?
Add the e-mail I pasted above to the matter as correspondence.

The names above are examples, not a real case.

Limits

  • 120 requests a minute per account.
  • add_document takes text or a file up to 10 MB; larger files and archives go through create_upload_link.
  • Upload links are valid for 30 minutes and work once.
  • Long documents come in windows; the assistant reads on with the offset the tool returns.
  • Asking questions costs no pages. Pages are counted when a document enters the case file, as with any import.

Security and privacy

  • The server acts as you: your role in each matter, your access to sensitive documents, the documents your team hid from you.
  • Every tool call is written to the matter's audit log with the assistant's name and the tool.
  • The owner of a firm can switch AI assistants off for all its matters under Settings → Organisation, and see and disconnect every connection.
  • Case documents are text written by others. The server tells the assistant to treat what it reads as data and never to follow instructions found in a document. No tool can send data outside Legalnaut; be careful when the same chat also has tools that can, such as e-mail or web access.
  • What the assistant reads is processed by its provider under your agreement with that provider.
  • Disconnect any assistant under Settings → AI assistants; its tokens stop working at once.

Troubleshooting

The assistant says it is not authorised, or the connection was disconnected.

Connect it again from the assistant. A disconnected connection never comes back on its own.

Tools such as add_document are missing.

The connection is read only. Disconnect it in Settings → AI assistants and connect again choosing "Read and change". Your role must also allow the change.

"Unknown matter".

Ask the assistant to call list_matters and use the key it returns.

"The firm that holds this matter has switched off AI assistants".

The firm's owner can switch them back on under Settings → Organisation.

"This matter is locked until a plan is chosen".

The trial ended or the subscription lapsed. Choose a plan in Legalnaut.

The sign-in window does not open.

Check that your browser allows pop-ups from the assistant, or copy the sign-in link it shows into the browser.

Tools such as add_document are missing on the demo account.

The shared demo account connects read only, so every visitor finds the demo case as they left it. Create your own account to add documents or record decisions.

Still stuck? Write to contact@legalnaut.com.

Server version

  • 1.0.0 (22 November 2026): first release, with OAuth sign-in, read and change access levels and eight workflows.