Oktopeak

[ OPEN-SOURCE · MIT · FIRST ON THE MCP REGISTRY ]

Lawmatics MCP Server — open-source Claude + Lawmatics integration

The first Lawmatics connector on the official Anthropic MCP Registry. Claude reads your matters, pipeline, custom fields, and intake forms directly from the Lawmatics API — with a read-only mode for cautious firms. MIT licensed, on npm.

37 tools

matters, pipeline, custom fields, forms, tasks, invoices

Read-only

one env var removes every write tool

One auth

Lawmatics tokens never expire — authorize once

YouWhich sources produced hired matters this quarter?

From your 214 matters, 38 hired:

Referrals17
Google LSA12
Past clients9

demo data

runs on your machine · read-only mode available

[ REAL FIRMS, REAL RECEIPTS ]

New: the first Lawmatics MCP connector on the Registry 1.1k+ installs across our five connectors Listed on Anthropic's MCP Registry MIT licensed — read every line

★★★★★

“Everything was done professionally, with efficient and fast communication, unconditional availability, kindness and professionalism.”

Goran Dojčinović Lawyer, Dojčinović Law Office

Verified review · Clutch, 5.0

“It’s very commendable — significant time went into that. Thank you both for open-sourcing it.”

Alexander W. Ostheimer-Lebeau Founder & Director, family-law firm (Ontario)

On our Clio connector · June 2026

Running on live dockets

A solo attorney found the connector on npm, installed it himself, ran Claude against his active matters, and emailed us a technically precise bug report the same week. The fix shipped. That is what real usage looks like.

[ TRY IT ]

Ask it something

Three real questions firms ask on day one, answered the way the connector answers them. Scripted demo with demo data — the live version answers about your pipeline.

Claude · connected to Lawmatics · demo data

YouWhich sources produced hired matters this quarter?

From your 214 matters this quarter, 38 hired:

Referrals17
Google LSA12
Past clients9

Tools used: list-matters (filter: status=hired) + list-sources · Claude did the cross-tab

Wired to your account, this is a 15-minute install. The setup guide · the source.

[ TWO WAYS TO RUN IT ]

Install it yourself, or have us put it in your firm

Install it yourself

Free under the MIT license, on npm and the official Anthropic MCP Registry. You need someone comfortable in a terminal, Developer Settings enabled on your Lawmatics account (a free support request), and about fifteen minutes. Nobody at Oktopeak touches your data or your credentials.

View on GitHub

We deploy it in your firm

We handle the Developer Settings request, the app registration, read-only or full rollout per your comfort level, the audit log wired into wherever your firm keeps records, and one working workflow designed with your intake team. You own the result and the code.

Guided setup for firms

[ QUICK INSTALL ]

Three steps, one-time auth

1. Get API access from Lawmatics (free, but gated)

Lawmatics doesn't switch on API access by default. Ask support or email api@lawmatics.com to enable Developer Settings on your account, then create an app under Settings → Developers with the callback URL http://localhost:5678/callback. You get a Client ID and Secret.

2. Run the one-time auth command

LAWMATICS_CLIENT_ID=xxx LAWMATICS_CLIENT_SECRET=yyy \
  npx -y @oktopeak/lawmatics-mcp auth

Approve access in your browser and the command prints your access token. Lawmatics tokens never expire, so this happens exactly once — store the token like a password.

3. Add to your Claude Desktop or Claude Code MCP config

{
  "mcpServers": {
    "lawmatics": {
      "command": "npx",
      "args": ["-y", "@oktopeak/lawmatics-mcp"],
      "env": {
        "LAWMATICS_ACCESS_TOKEN": "your-token-here"
      }
    }
  }
}

Restart Claude and ask "Who am I logged in as in Lawmatics?" to verify. Add "LAWMATICS_READ_ONLY": "1" to the env block if you want lookups and reporting with zero write access.

[ EVERY TOOL, FROM THE SOURCE ]

All 37 tools — plus the one behind a flag

Generated from the connector's source, not a marketing list. 26 read tools, 11 write tools (all removed by LAWMATICS_READ_ONLY=1), and one experimental tool gated until a live account confirms Lawmatics' undocumented write format.

list-mattersREAD

List matters (leads/prospects/clients) with optional filter, sort, and pagination.

Matters

get-matterREAD

Get full details for a single matter by ID, including custom fields and related records (contact, stage, practice area, tasks, notes, events, invoices as id/type refs

Matters

find-matterREAD

Find a single matter by exact email, phone, or name.

Matters

create-matterWRITE

Create a new matter (lead).

Matters

update-matterWRITE

Update a matter.

Matters

list-contactsREAD

List contacts (people) with optional filter, sort, and pagination.

Contacts

get-contactREAD

Get full details for a single contact by ID, including custom fields.

Contacts

find-contactREAD

Find a single contact by exact email, phone, or name.

Contacts

create-contactWRITE

Create a new contact (person) without a matter.

Contacts

update-contactWRITE

Update a contact.

Contacts

list-companiesREAD

List companies with optional filter, sort, and pagination.

Companies

get-companyREAD

Get full details for a single company by ID.

Companies

find-companyREAD

Find a single company by exact email, phone, or name.

Companies

list-pipelinesREAD

List the firm's pipelines with matter counts, estimated value, and stage references.

Pipeline & firm data

list-stagesREAD

List all pipeline stages.

Pipeline & firm data

list-practice-areasREAD

List the firm's practice areas (id, name, color).

Pipeline & firm data

list-sourcesREAD

List marketing sources (where leads come from: Google, referrals, etc.).

Pipeline & firm data

list-sub-statusesREAD

List matter sub-statuses.

Pipeline & firm data

list-usersREAD

List the firm's Lawmatics users (staff).

Pipeline & firm data

get-current-userREAD

Get the user the access token belongs to.

Pipeline & firm data

list-tasksREAD

List tasks with optional filter, sort, and pagination.

Tasks

create-taskWRITE

Create a task, optionally attached to a matter/contact/company and assigned to users.

Tasks

update-taskWRITE

Update a task — e.g.

Tasks

list-eventsREAD

List events (appointments) with optional filter, sort, and pagination.

Events

create-eventWRITE

Create an event (appointment), optionally attached to a matter or contact and with user hosts.

Events

list-notesREAD

List notes with optional filter, sort, and pagination.

Notes & timeline

create-noteWRITE

Create a note on a matter, contact, or company.

Notes & timeline

list-activitiesREAD

List timeline activities (audit trail of everything that happened: notes, emails, stage moves...).

Notes & timeline

list-tagsREAD

List the firm's tags.

Tags

attach-tagsWRITE

Attach tags to a matter, contact, company, or task.

Tags

detach-tagsWRITE

Detach tags from a matter, contact, company, or task.

Tags

list-custom-fieldsREAD

List the firm's custom field definitions (id, name, field_type, owner type, list options).

Custom fields

set-matter-custom-fieldsEXPERIMENTAL

EXPERIMENTAL (unverified against a live account — enable via LAWMATICS_EXPERIMENTAL_TOOLS=1): set custom field values on a matter.

Custom fields

list-formsREAD

List the firm's custom forms (intake forms).

Intake forms

get-formREAD

Get one custom form including its field layout (field IDs, labels, types, required flags).

Intake forms

get-form-entriesREAD

List submissions for a custom form, each with label/value pairs and the matter it created.

Intake forms

submit-formWRITE

Submit an entry to a custom form — creates a matter/contact and fires the form's automations, exactly like a website submission.

Intake forms

list-invoicesREAD

List invoices (read-only in the Lawmatics API).

Billing

Every tool's implementation is public: read the source on GitHub.

[ MORE THAN ONE ATTORNEY? ]

Setting this up for the whole firm?

The install above is one laptop, one login — right for a solo attorney or a first test. A firm means repeating it on every machine, with no shared record of who did what. We deploy the same connector from one place your firm controls: each person signs in as themselves, and there is one audit log for the whole firm.

[ WHAT MAKES OURS DIFFERENT ]

The only Lawmatics connector with a real read-only mode

YOUR MACHINE Claude Desktop / Code @oktopeak/lawmatics-mcp token, local audit log LAWMATICS_READ_ONLY=1 removes every write tool api.lawmatics.com MCP HTTPS
Claude ↔ connector (on your machine) ↔ Lawmatics. Token stays local. Every call written to an append-only log. Nothing routes through Oktopeak.

Config-level read-only mode

The Lawmatics API has no permission scopes — any token can write. Set LAWMATICS_READ_ONLY=1 and every write tool is removed from the server entirely, not just blocked. Reporting without risk, on day one.

Local audit log

Every tool call — name, arguments, outcome — appended to a local JSONL file on your machine. A firm admin can always answer "what did the AI touch," and the log never leaves the building.

Honest about its edges

Built strictly from the official API docs with 87 tests locking the contract, and not yet verified against a live firm account — the README says so. Where Lawmatics under-documents (custom-field writes), tools ship behind an experimental flag instead of a guess.

Lawmatics is one of five systems we've built this for — same architecture for Clio, MyCase, Filevine, and IntakeQ. See the whole set in the MCP Connectors case study.

[ THE #1 USE CASE ]

The reporting layer Lawmatics doesn't ship

"Matters by source and practice area, with the intake custom fields, for last quarter" — native reports wall on it, the CSV export drops matter fields, and Zapier can't touch custom fields at all. Through the connector, Claude pulls the raw records and does the aggregation itself. Ask the question, get the table.

We mapped all four ways to get pipeline data out of Lawmatics — native reports, CSV, Zapier, and the API route — with the walls each one hits.

Read the reporting guide

[ OTHER WAYS TO CONNECT ]

Weighing this against Zapier?

Fair question — Zapier's Lawmatics app is the incumbent route. It wins on event triggers today; it can't read pipelines, invoices, or any custom field, and every synced record bills a task. We wrote the honest side-by-side, including where Zapier is the right answer.

Read the comparison

Running Lawmatics next to Clio? The two-system stack breakdown covers what gets paid for twice and when consolidation makes sense.

[ PRIVILEGE-SAFE DEPLOYMENT ]

Want to run this with a local LLM instead of consumer Claude?

For firms with maximum confidentiality requirements, the same Lawmatics MCP server pairs with LM Studio or Continue.dev running a local model on your hardware. Full guide is the Privilege Stack post.

Read the Privilege Stack guide

[ FAQ ]

Lawmatics MCP Server — frequently asked

An open-source Model Context Protocol implementation that connects Claude AI (or any MCP-compatible client) directly to Lawmatics legal CRM. 37 tools across matters, contacts, companies, pipelines, stages, practice areas, marketing sources, tasks, events, notes, tags, custom fields, intake forms, and invoices. Published on npm as @oktopeak/lawmatics-mcp, and the first Lawmatics connector listed on the official Anthropic MCP Registry as io.github.oktopeak/lawmatics-mcp. MIT licensed.
Three steps. First, ask Lawmatics support (or email api@lawmatics.com) to enable Developer Settings on your account — it's free, just not on by default — and create a developer app under Settings → Developers. Second, run the one-time auth command: npx @oktopeak/lawmatics-mcp auth. Because Lawmatics access tokens never expire, you do this exactly once. Third, paste the token into your Claude Desktop or Claude Code config. The full 15-minute guide walks through every step.
Yes, and this is the connector's signature feature: set LAWMATICS_READ_ONLY=1 in the config and every write tool (create, update, tag, form submit) is removed entirely — they don't exist as far as Claude is concerned. Reporting and lookups keep working. Recommended for a first rollout and for firms that want AI answers without AI hands.
The server runs locally on your machine and talks only to api.lawmatics.com. Your access token lives in your own config file; nothing routes through Oktopeak servers and there is no telemetry. Every tool call is appended to a local audit log at ~/.lawmatics-mcp/audit.log so a firm admin can always answer "what did the AI touch." One honest caveat: the Lawmatics API has no permission scopes, so any token has full account access — which is exactly why the read-only mode and the audit log exist. For the deployment patterns cautious firms use, see the Privilege Stack guide.
Not yet, and we say that plainly rather than implying otherwise. The connector is built strictly against the official Lawmatics API documentation and its published example payloads, with 87 unit tests locking in that contract, and it went through an adversarial review before release. Where Lawmatics under-documents something (custom-field writes), those tools ship behind an experimental flag instead of a guess. If you hit a mismatch with the real API, open an issue — that's the point of it being open source.
Not yet. Claude Cowork and claude.ai only accept remote MCP servers, and this connector currently ships stdio transport for Claude Desktop, Claude Code, and other local MCP clients. Running it as a hosted service your whole firm signs into is a deployment job rather than a config edit — that's what our Firm-Wide Deployment engagement covers.
The connector is free under the MIT license, and unlike Zapier there is no per-task metering — the only marginal cost is the Claude subscription you already have. If you want us to set it up for your firm with scoped rollout, the audit log wired into your records, and one working workflow, that is our guided setup for firms. For work beyond the connector — Lawmatics↔Clio sync, intake automation rescue, custom reporting — see Lawmatics integration services.
No — it works with the Lawmatics subscription you already have, on any plan with API access (Pro and up). If the bigger spend question is on your mind, we published the honest math: what Lawmatics actually costs over three years, including the real bill of a 9-attorney firm. Worth reading before any renewal.

Still have questions?

Talk with a friendly expert

[ GET STARTED ]

Start with the free connector. Hire us if you need help.

Two paths: install the OSS yourself (free, MIT, on GitHub), or have us deploy it in your firm — Developer Settings request handled, read-only or full rollout per your comfort, audit log wired in, one workflow built with your intake team.

Takes about a minute, and you get the Developer Settings request your firm needs either way. Or book a 30-minute call instead.

We asked sixty lawyers what actually eats their day. The findings are free.