Open-source MCP servers

Connect Claude to the software your law firm already runs on.

Three MCP servers for Lawmatics, DecisionVault and WealthCounsel. Read and update your CRM, intake and matters just by asking. No Zapier, no copy-paste, and nothing routed through anyone else's servers.

What these MCP servers do

Estate-planning firms run on a stack that does not talk to itself. Lawmatics holds the CRM, DecisionVault holds the intake questionnaires, WealthCounsel holds the contacts and matters. Getting a straight answer means opening three tabs.

These are three independent MCP servers, one per system. Install only the ones your firm uses. Once connected, Claude can read and write to each of them while you talk to it in plain English.

Everything runs locally in Claude Code. Your access keys and your client data stay on your own computer and go straight to your software, which is the right architecture for privileged material.

Things you can ask

List my pipelines in Lawmatics.

Show me the intake for the Smith matter.

Which prospects have gone quiet for more than two weeks?

Pull the contacts and matters for this client across all three systems.

Update this prospect's custom fields with what we just discussed.

How to set up a Lawmatics, DecisionVault or WealthCounsel MCP server

You need Node.js 18 or newer and Claude Code.

git clone https://github.com/redwoodmeridian/ep-legal-mcps.git
cd ep-legal-mcps
claude

Then just tell Claude, in plain English:

Help me set up the Lawmatics tool.

Claude finds your access key with you, switches the server on and tests it. Prefer to do it yourself? Each tool ships a one-command installer:

cd lawmatics-mcp && ./setup.sh

Your keys live in ~/.config/ on your machine and are never stored in the repo.

What's inside the repo

ServerWhat it does
lawmatics-mcpLawmatics — CRM and case management. For firms running on Lawmatics.
decisionvault-mcpDecisionVault — client intake questionnaires.
wealthcounsel-mcpWealthCounsel — contacts and matters. For estate-planning firms.
GET-STARTED.mdThe full walkthrough, including what is and is not supported.
CLAUDE.mdOperating instructions Claude reads when you open the repo.

Frequently asked questions

Is there an MCP server for Lawmatics?

Yes. lawmatics-mcp in this repo is an open-source MCP server that connects Claude to the Lawmatics API for CRM, pipelines, prospects, matters and custom fields. It runs locally in Claude Code under the MIT License.

Is there an MCP server for DecisionVault or WealthCounsel?

Yes, both. decisionvault-mcp covers client intake questionnaires and wealthcounsel-mcp covers contacts and matters. They are independent. Install only the ones your firm actually uses.

Is it safe to connect client data to Claude this way?

These servers run locally on your own machine. Your access keys and client data go straight from your computer to your software and are never routed through a third-party server. That local-only architecture is what makes it an appropriate fit for privileged client material.

Does this work with Claude.ai or Claude Cowork?

Not yet. Those connect to tools from the cloud and need a hosted server. These are local MCP servers for Claude Code. See GET-STARTED.md for detail.

What do I need to install?

Node.js 18 or newer and Claude Code. Then clone the repo and ask Claude to set up the tool you use. It handles the rest.

Who made these MCP servers?

Irfad Imtiaz, Director of Technology at My Legal Academy, built and maintains them. My Legal Academy publishes them.

Who built Estate Planning Legal MCPs

Irfad Imtiaz built and maintains Estate Planning Legal MCPs. He is Director of Technology at My Legal Academy, which publishes this kit and uses it with the law firms it works with. My Legal Academy trains firm owners to run their practice with AI through its AI Labs program and done-for-you build engagements.

Find him at irfad.me, LinkedIn and GitHub.

More open-source kits by Irfad Imtiaz