Compare Lawmatics MCP servers
Verified from each project's source and docs. Facts, not verdicts — you draw the conclusion.
| Weave Legal | redwoodmeridian | dschnurbusch | HarderBetterFaster |
|
|---|---|---|---|---|
| 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
|
🟡 Token in env (OAuth helper) | 🔴 API token in env | 🔴 API token in env |
| Access governance | 🟢 Centralized
|
🔴 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 — you sign in and go. 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 the ability to revoke a session instantly is a materially stronger posture.
Team vs. solo
Single-account servers assume one person, one firm. If several people at a firm — or a firm managing multiple Lawmatics accounts — need access, you 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 when someone leaves. Centralized control (an 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 or create an account →The directory
Weave Legal
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.
dschnurbusch/lawmatics-mcp-server
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.
redwoodmeridian/ep-legal-mcps
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.
HarderBetterFasterStronger/lawmatics-mcp
A Lawmatics-branded npm package with ~20 tools. Dormant since May 2025. Self-hosted, single account, stdio.
Best for: a quick, minimal stdio setup.