# The Lawmatics MCP Directory

> Every way to connect Lawmatics to Claude and other AI, compared. An independent directory maintained by [Weave Legal](https://weave.legal).

## Compare Lawmatics MCP servers

Verified from each project's source and docs. Facts, not verdicts.

| Criterion | Weave Legal | redwoodmeridian | dschnurbusch | HarderBetterFasterStronger |
|---|---|---|---|---|
| Status | 🟢 In production | 🟢 Active | 🔴 Dormant (since June 2026) | 🔴 Dormant (since May 2025) |
| Tools | 100+ | 24 | 100+ | ~20 |
| Built for | Solo, Teams, Firms | Solo | Solo | Solo |
| Hosted | 🟢 Yes | No (self-host) | No (self-host) | No (self-host) |
| Security | 🟢 Enterprise-grade — OAuth 2.0 + Google SSO; encrypted token store; per-session revocation | 🟡 Token in env (OAuth helper) | 🔴 API token in env | 🔴 API token in env |
| Access governance | 🟢 Centralized — allowed-email control, per-firm scoping, instant per-session revocation | 🔴 None | 🔴 None | 🔴 None |

## What to look for in a Lawmatics MCP

- **Hosted vs. self-host** — A hosted service is always on and needs no setup. A self-hosted repo means you clone it, supply credentials, and keep it running yourself. Great for developers; a hurdle for everyone else.
- **Auth & security** — Most open-source options put a long-lived Lawmatics API token in an environment file; anyone with that file has full access. OAuth with SSO, an encrypted token store, and instant session revocation is a materially stronger posture.
- **Team vs. solo** — Single-account servers assume one person, one firm. Firms with several users — or managing multiple Lawmatics accounts — want multi-firm support and per-user identity, not a shared token.
- **Access governance** — Who can connect, which account they reach, and how fast you can cut off access. Centralized control (allowed-email list, per-firm scoping, per-session revocation) is the difference between a hobby tool and something a firm can run responsibly.

## Want it hosted, secured, and team-ready?

Weave Legal connects Lawmatics — and the rest of your firm's tools — to the AI you already use, with central control and no setup.

- Explore Weave Legal: https://weave.legal/integrations
- Create an account: https://accounts.weave.legal/sign-up

## The directory

### Weave Legal — hosted
Hosted, OAuth-secured, multi-firm Lawmatics MCP with a central admin dashboard. No servers to run, no tokens in a config file. **Best for:** firms and teams who want it to just work, with central control over who can access what. → https://weave.legal/integrations

### dschnurbusch/lawmatics-mcp-server — open source
The broadest open-source tool surface (100+), with dry-run previews and confirm-on-delete safety. Self-hosted, single account, stdio. **Best for:** solo developers who want maximum coverage and don't mind self-hosting. (npm: `lawmatics-mcp-server`) → https://github.com/dschnurbusch/lawmatics-mcp-server

### redwoodmeridian/ep-legal-mcps — open source
A curated 24-tool set with one-command setup and a bundled OAuth helper. Actively maintained. Self-hosted, single account, stdio. **Best for:** a single firm wanting a clean, supported self-host. → https://github.com/redwoodmeridian/ep-legal-mcps/tree/main/lawmatics-mcp

### HarderBetterFasterStronger/lawmatics-mcp — open source
A Lawmatics-branded npm package with ~20 tools. Dormant since May 2025. Self-hosted, single account, stdio. **Best for:** a quick, minimal stdio setup. (npm: `@lawmatics/mcp`) → https://github.com/HarderBetterFasterStronger/lawmatics-mcp

---

Independent directory maintained by Weave Legal. "Lawmatics" is a trademark of its respective owner; this site is not affiliated with or endorsed by Lawmatics.