Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Lawmatics to Claude Code

Make Claude run client intake and matters in Lawmatics. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Lawmatics to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Lawmatics, you add a Lawmatics MCP server: a small hosted service that exposes Lawmatics's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Lawmatics account. No API keys pasted into config files.

claude mcp add --transport http lawmatics https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Lawmatics once connected?

Full read-write means Claude can pull a matter with its contact, stage, and custom fields, create new prospects from inbound leads, update matters as intake progresses, and assign follow-up tasks. Pipeline questions get instant answers, and every write to a matter or contact waits for approval.

  • Look up a matter with its contact, pipeline stage, and custom field values
  • Summarize the intake pipeline and flag prospects with no recent activity
  • Create a new prospect and contact from an inbound lead, after you approve
  • Update a matter's details or custom fields as intake progresses, after you approve
  • Create follow-up tasks assigned to staff, after you approve
  • Add a note to a matter or contact for your review

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Lawmatics access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Lawmatics API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Lawmatics changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Lawmatics connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Lawmatics connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Lawmatics account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Lawmatics's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Lawmatics?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Lawmatics account it signs in with. Revoking access is one click in Lawmatics.

More on the Lawmatics connector

Lawmatics connector for claude.aiClio + Claude CodeMyCase + Claude CodePracticePanther + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us