Interoperability

Connect your AI to MatterFirst

MatterFirst speaks the Model Context Protocol. Whatever your firm uses to think with, Claude, Copilot, CoCounsel, Harvey, or something you wrote yourselves, it can read your matters, your documents and your deadlines directly, and ask MatterFirst to do things that a person at the firm then approves.

This is not a competing assistant. MatterFirst is your system of record: point your AI at it.

What a connected client can do

Answer questions from your own file
"What settlements do we have in the next fortnight." "Which matters are waiting on finance approval." "What did we tell the vendor's solicitor about the special conditions." Answered from your records, with the document and page each answer came from.
Read a matter as context
A matter attaches to a conversation as a resource, so your assistant starts from the file rather than searching for it. Its extracted facts come with it: parties, key dates, amounts, obligations, risks, each with the excerpt it was taken from.
Ask for something to be done
And that is where it stops. Read on.

Nothing outside MatterFirst can change your files

Every tool that would change something submits a request instead. Sending an email, creating a task, closing a matter, recording a fact: each one appears in MatterFirst for a person at your firm to read and approve, and nothing happens until they do.

We think this is the only defensible way to expose a legal system of record, and we would rather say so plainly than have you discover the alternative. An assistant that can close a matter because it misunderstood a sentence is not a productivity gain.

That is the setting every tool arrives with. A firm that has decided a particular one is safe in its hands can waive the approval for that tool alone, and we would rather that be a switch you can find than something you work around. The request is still recorded either way, against the person whose access was used.

Two further controls, both yours. A firm is reachable only once an owner or admin allows it, and withdrawing that closes the door at once. And each of the tools can be refused to outside apps while your own people keep using it. A connected app otherwise works with everything the person who connected it can see, including document text, so use AI accounts set to zero data retention.

Connecting

There is nothing to install and no key to copy. You give your AI app one address, it sends you to MatterFirst to sign in, and it then works as you: it sees the matters you can see and nothing else.

  1. 1. An owner or admin allows it once for the firm: in MatterFirst, open Settings, Where data can go, and switch on AI apps your team connects. It is off until they do.
  2. 2. Each person opens Settings, Connect an AI app, copies the address and follows the steps for their app. The same steps are below.

The address: https://matterfirst.com/mcp

Claude

  1. 1. In Claude, open Settings, then Connectors, and choose "Add custom connector".
  2. 2. Name it MatterFirst, paste your MatterFirst address as the URL, and choose Add. Leave the advanced OAuth boxes empty.
  3. 3. Choose Connect beside MatterFirst and sign in when Claude sends you here.
  4. 4. In a chat, switch MatterFirst on under the tools menu, then ask about a matter.

Works in claude.ai and the Claude desktop and mobile apps. Custom connectors are on Claude's paid plans; on a team plan an owner may need to add it once for everyone.

ChatGPT

  1. 1. In ChatGPT, open Settings, then Apps & Connectors, and choose to create one.
  2. 2. Name it MatterFirst, paste your MatterFirst address as the server URL, keep OAuth as the sign-in method, and choose Create.
  3. 3. Sign in to MatterFirst when ChatGPT sends you here.
  4. 4. In a chat, add MatterFirst from the tools menu, then ask about a matter.

If you can't see the option to create one, switch on Developer mode under Apps & Connectors, Advanced settings first.

Claude Code

  1. 1. Run the line below in your terminal.
  2. 2. Start Claude Code, type /mcp, choose matterfirst and sign in. 
claude mcp add --transport http matterfirst https://matterfirst.com/mcp

Codex, Cursor, VS Code and other editors

  1. 1. Add the block below to your editor's MCP settings, or paste it to the editor's assistant and ask it to add MatterFirst.
  2. 2. Sign in to MatterFirst when the editor sends you here. 
{
  "mcpServers": {
    "matterfirst": {
      "type": "http",
      "url": "https://matterfirst.com/mcp"
    }
  }
}

A script or your own software needs a key

  1. 1. Ask an owner or admin for a key from Settings, AI app connections.
  2. 2. Send it as a bearer token to your MatterFirst address, as in the block below. 
{
  "mcpServers": {
    "matterfirst": {
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      },
      "type": "http",
      "url": "https://matterfirst.com/mcp"
    }
  }
}

A key acts as the person it was issued to. Use one per machine, so losing one means revoking one.

For the person setting this up

Endpoint
https://matterfirst.com/mcp
Transport
Streamable HTTP. stdio is not offered: every consumer here is remote.
Protocol
2025-06-18, 2025-03-26
Authorization
OAuth 2.1 with PKCE and dynamic client registration against your MatterFirst sign-in, or a bearer key issued in the app for software that cannot sign in. Metadata at /.well-known/oauth-protected-resource.
Discovery
/.well-known/mcp
Rate limit
Per connection, set by the firm. 120 calls a minute by default.
Audit
Every call is recorded against the firm, with the client that made it and whether it was answered or refused.

Questions, or a client that does not connect: tell us what it said and we will make it work.