Lawmatics MCP Server

Lawmatics MCP Server

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.

→ See Guided MCP Setup — or book a 30-min call

Jump to: What it does · Installation · Getting API access · Available tools · Read-only mode · Security · Known API limitations

---

What it does

Once connected, Claude can talk directly to your Lawmatics firm data. You can ask things like:

• "How many open PNCs do we have per practice area?"
• "Which marketing source brought in the matters we actually hired this quarter?"
• "Show me every matter sitting in the 'Consult Completed' stage with no task attached"
• "Export all personal injury leads from July with their custom intake fields"
• "What did the Smith intake form submissions say this week?"
• "Create a follow-up task for the Jones matter, due Friday, assigned to Sarah"

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.

Project status

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.

---

Prerequisites: getting Lawmatics API access

• Node.js 18+
• A Lawmatics account with admin access
• Developer Settings enabled on your account. Lawmatics gates API access behind a support request: contact Lawmatics support or email api@lawmatics.com and ask them to enable Developer Settings. It's free; it's just not on by default.
• A developer app: once Developer Settings is on, go to Settings → Developers in Lawmatics, create an app, and set the Callback URL to http://localhost:5678/callback. You'll get a Client ID and Client Secret.

Get your access token (one time)

Lawmatics access tokens never expire, so you do this exactly once:

LAWMATICS_CLIENT_ID=your_client_id LAWMATICS_CLIENT_SECRET=your_client_secret npx -y @oktopeak/lawmatics-mcp auth

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.

Installation

With Claude Desktop (recommended)

Add this to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Restart Claude Desktop. Ask "Who am I logged in as in Lawmatics?" to verify the connection (it calls get-current-user).

With Claude Code

claude mcp add lawmatics -e LAWMATICS_ACCESS_TOKEN=your_token_here -- npx -y @oktopeak/lawmatics-mcp

---

Available tools

37 tools. Matters are what Lawmatics calls "prospects" internally — every lead and case, whether PNC, hired, or lost.

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.

Custom fields

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).

Read-only mode

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.

Configuration reference

Security

• Your token stays on your machine. It lives in your MCP config file and is sent only to api.lawmatics.com. This server has no backend, no telemetry, and phones home to no one.
• Audit log. Every tool call (name, arguments, outcome) is appended to a local JSONL file at ~/.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.
• Least privilege caveat. The Lawmatics API has no scopes: any token has full CRUD access. Read-only mode is enforced by this server, not by Lawmatics — pair it with the audit log, and delete the developer app to revoke access entirely.
• Data flow. Records Claude requests flow from Lawmatics through this local process into your MCP client and its model context. Review your AI provider's data handling terms the same way you would for any vendor touching client data.

Known Lawmatics API limitations

Things this connector cannot do because the underlying API doesn't support them (as of API v1.22):

• No pipeline stage moves. The API exposes stages read-only; sub_status_id on update-matter is the closest control.
• One filter per request. Complex queries need fetch_all + letting Claude filter the result.
• Page size is fixed at 25. Large exports take one request per 25 records (the built-in throttle respects the rate limit).
• Invoices, pipelines, sources, campaigns are read-only.
• No e-signature, document templates, email sending, or automation management via API.
• Webhooks are configured in the Lawmatics dashboard only (no API management).

Roadmap

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.

Other connectors by Oktopeak

• Clio MCP — Clio practice management
• MyCase MCP — MyCase practice management
• Filevine MCP — Filevine case management
• IntakeQ MCP — IntakeQ / PracticeQ intake (healthcare)

Need more than the connector?

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

Development

npm install
npm test          # 80+ unit tests against the documented API contract
npm run build
npm run inspect   # MCP Inspector against the built server

Contributions welcome — especially reports from live Lawmatics accounts.

License

MIT © Oktopeak