The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Lawmatics MCP listing page.
Connect Claude to your Lawmatics legal CRM. Ask Claude to pull pipeline reports Lawmatics can't build natively, look up matters and contacts, check intake form submissions, create follow-up tasks — all without leaving your conversation.
Built by Oktopeak — AI transformation & automation for law firms
Digital transformation for legal and healthcare businesses. We build AI integrations, workflow automation, and custom software your firm owns outright — including this connector. → Book a 30-min call
[!TIP] Not a developer? You don't need to be.
The README below assumes someone comfortable editing a JSON config file. If that's not you or your team, we deploy this for law firms — scoped credentials, read-only mode if you want it, audit log wired in, one custom workflow, training.
Jump to: What it does · Installation · Getting API access · Available tools · Read-only mode · Security · Known API limitations · Other connectors · Need it deployed for you?
Once connected, Claude can talk directly to your Lawmatics firm data. You can ask things like:
Lawmatics' built-in reporting is a common complaint among firms. With this connector, Claude becomes the reporting layer: it pulls raw records (including custom fields) and does the aggregation, cross-tabbing, and formatting itself.
This server is built strictly against the official Lawmatics API documentation (v1.22) and its published example payloads, with 80+ unit tests locking in the documented request/response contract. It has not yet been run against a live firm account — if you hit a mismatch with the real API, open an issue with the tool name and the error text. That's the point of it being open source: real-world reports make it solid for everyone.
http://localhost:5678/callback. You'll get a Client ID and Client Secret.Lawmatics access tokens never expire, so you do this exactly once:
Open the printed URL, approve access, and the command prints your token plus a ready-to-paste config snippet. Store the token like a password — anyone holding it has full access to your firm's Lawmatics data until you delete the developer app.
Add this to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Restart Claude Desktop. Ask "Who am I logged in as in Lawmatics?" to verify the connection (it calls get-current-user).
37 tools. Matters are what Lawmatics calls "prospects" internally — every lead and case, whether PNC, hired, or lost.
| Group | Tools |
|---|---|
| Matters | list-matters, get-matter, find-matter (by email/phone/name), create-matter, update-matter |
| Contacts | list-contacts, get-contact, find-contact, create-contact, update-contact |
| Companies | list-companies, get-company, find-company |
| Pipeline & firm data | list-pipelines, list-stages, list-practice-areas, list-sources, list-sub-statuses, list-users, get-current-user |
| Tasks | list-tasks, create-task, update-task |
| Events | list-events, create-event |
| Notes & timeline | list-notes, create-note, list-activities |
| Tags | list-tags, attach-tags, detach-tags |
| Custom fields | list-custom-fields (+ experimental set-matter-custom-fields, see below) |
| Intake forms | list-forms, get-form, get-form-entries, submit-form |
| Billing | list-invoices (read-only in the Lawmatics API) |
Every list tool supports the full Lawmatics query surface: one filter (filter_by / filter_on / filter_with with =, !=, <, >, like, ilike, null, not_null), sorting, field selection (fields, including custom_fields), and pagination — plus a fetch_all option that follows pagination up to 1,000 records and always tells you if the result was truncated.
Lawmatics firms live in custom fields. To read them, add custom_fields to the fields parameter of any get/list tool. list-custom-fields shows every field definition including picklist options, so Claude can interpret raw values.
Writing custom field values is only loosely documented by Lawmatics, so set-matter-custom-fields ships behind a flag until someone with a live account confirms the request shape (set LAWMATICS_EXPERIMENTAL_TOOLS=1 to enable it — and please report whether it works).
Set LAWMATICS_READ_ONLY=1 in the server's env config and every write tool (create/update/tag/submit) is removed entirely — not just blocked, they don't exist as far as Claude is concerned. Recommended for a first rollout, for reporting-only use, and for cautious partners.
| Env var | Purpose |
|---|---|
LAWMATICS_ACCESS_TOKEN | Required. Your OAuth access token (never expires). |
LAWMATICS_READ_ONLY | 1 = disable all write tools. |
LAWMATICS_EXPERIMENTAL_TOOLS | 1 = enable tools whose API shape Lawmatics hasn't fully documented. |
LAWMATICS_RATE_LIMIT_PER_MIN | Client-side throttle. Default 50 (Lawmatics documents both 50/min and 150/min; we default to the safe one). |
LAWMATICS_AUDIT_LOG | 0 = disable the local audit log. |
LAWMATICS_AUDIT_LOG_PATH | Audit log location (default ~/.lawmatics-mcp/audit.log). |
LAWMATICS_CLIENT_ID / LAWMATICS_CLIENT_SECRET | Only for the one-time auth command. |
LAWMATICS_REDIRECT_PORT | OAuth callback port (default 5678). |
LAWMATICS_API_BASE | API base override (default https://api.lawmatics.com/v1). |
api.lawmatics.com. This server has no backend, no telemetry, and phones home to no one.~/.lawmatics-mcp/audit.log, so a firm admin can always answer "what did the AI touch." Note that tool arguments can include client data (names, emails, note text) — the log lives only on your machine, but include it in your firm's data retention policy, or disable it with LAWMATICS_AUDIT_LOG=0.Things this connector cannot do because the underlying API doesn't support them (as of API v1.22):
sub_status_id on update-matter is the closest control.fetch_all + letting Claude filter the result.File upload/download, time entries and expenses, relationships, task subtasks/comments, and Collections (Lawmatics' custom data tables) — in rough order of demand. Open an issue if you need one sooner.
Each connector has its own overview page on oktopeak.com with setup notes and FAQ:
Same architecture, same audit logging. All MIT licensed.
The connector is free and stays free. Firms hire us for what's around it: deployment on every attorney's machine, scoped credentials, custom workflows ("every morning, list yesterday's new leads by source with intake answers"), integrations Lawmatics doesn't have, and the production software layer when you outgrow Zapier.
→ Guided MCP Setup · Book a 30-min call
→ Firm-wide deployment: rolling Claude + this connector out to a whole firm (Claude Cowork, multi-user, security review)? See Firm Deployment.
Want a polished overview of this connector with FAQ? → oktopeak.com/lawmatics-mcp/
This connector is free, MIT licensed, and maintained by Oktopeak. It always will be; we don't take donations. If it saved you time, the things that actually help:
Contributions welcome — especially reports from live Lawmatics accounts.
MIT © Oktopeak