Triages NDAs, reviews contracts against your playbook, tracks renewals, and checks the case law and regulations behind a question.
Built for: The in-house counsel or operations lead reviewing contracts for a company that has no legal team, or a legal team of one.
The button opens the checkout, where the 5 servers and 6 skills are listed one by one. Every member is free, so the checkout lists them and asks for no card.
The reason to buy a stack rather than five listings: each line below needs more than one member connected at the same time.
Triage an NDA and, where it needs changes, make them in Word as tracked changes with comments.
Review a vendor or SaaS agreement against your playbook, flag the deviations and propose the redline.
Check a cited US case on CourtListener, or the current consolidated text of an EU regulation, before relying on it.
Keep the renewal register current and warn before an auto-renewal notice window closes.
What each part contributes, and why it was picked over the obvious alternative. Prices and permissions are read from the listings, so nothing here can disagree with the catalogue.
Edits the contract in Microsoft Word with real tracked changes and threaded comments under your name — a redline, not a rewritten file.
PandaDoc's hosted server for creating, sending, signing and tracking documents once the terms are agreed.
US court opinions, dockets, citations and judges from CourtListener, for checking the case a clause relies on.
EU law from EUR-Lex: regulations, directives, consolidated texts, case law and national transposition.
The US Electronic Code of Federal Regulations, including FAR and DFARS, with version history and recent changes.
Sorts an incoming NDA into standard, needs review or significant issues, so counsel reads only the ones that need it.
Reviews a contract clause by clause against your negotiation playbook and proposes redline language.
The terms that matter in a SaaS deal — auto-renewal, price escalation, data portability, SLAs, subprocessors.
GDPR and CCPA questions, data processing agreements and data subject requests.
Classifies a risk by severity and likelihood and says when it needs senior or outside counsel.
Keeps a register of cancel-by dates and warns before a notice window closes.
Every member is free, so the monthly figure is $0 whatever you do with the stack: nothing here is billed by the call, and only adding a paid member could change it.
| Part | What you are paying for | Monthly, as quoted |
|---|---|---|
| Word Mcp Live | Free | — |
| PandaDoc | Free | — |
| Courtlistener | Free | — |
| Eurlex | Free | — |
| eCFR | Free | — |
| Skills | ||
| NDA Triage | Free · context cost only | — |
| Contract Review | Free · context cost only | — |
| SaaS / Subscription Agreement Review | Free · context cost only | — |
| Compliance | Free · context cost only | — |
| Legal Risk Assessment | Free · context cost only | — |
| /renewal-tracker | Free · context cost only | — |
| Everything above | $0 of servers plus $0 of skills, the same in a quiet month and a busy one | $0/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months.
Install only these and the bill is nothing: 5 servers and 6 skills, and all 144 tools.
Nothing in this stack carries a call allowance, so nothing here can run out before the month does. The bill is decided when you install it, not when you use it.
The spend cap is one figure for the whole account, set in your dashboard and checked when an order is placed. On the call path what stops a retry loop is the plan's call allowance and its rate limit, and a refused call is never billed.
The steps below come before the install lines: what to decide and scope before connecting anything, in the order it matters. The lines themselves follow, part by part, for the client you pick.
npx mcprush@latest stack add legal-desk writes all 5 servers into Claude Code’s config in one go — or run the lines below one by one. The 6 skills are not included — add them with lines 06–11.
COURTLISTENER_API_TOKEN — CourtListener API token from your account settingsSet it where you start Claude Code — export COURTLISTENER_API_TOKEN=… in your shell profile on macOS and Linux, setx COURTLISTENER_API_TOKEN "…" on Windows, then open a new terminal. Claude Code reads it at start; the config keeps only the name.
# 01 · Word Mcp Live
claude mcp add --scope user word-mcp-live '--' uvx --from word-mcp-live word_mcp_server
# 02 · PandaDoc
claude mcp add --scope user --transport http pandadoc-mcp https://mcp.pandadoc.com/v1/mcp
# 03 · Courtlistener
claude mcp add --scope user --env 'COURTLISTENER_API_TOKEN=${COURTLISTENER_API_TOKEN}' --transport stdio courtlistener-mcp '--' npx -y @cyanheads/courtlistener-mcp-server
# 04 · Eurlex
claude mcp add --scope user eurlex-mcp '--' npx -y eurlex-mcp-server
# 05 · eCFR
claude mcp add --scope user 1102tools-ecfr-mcp '--' uvx ecfr-mcp
# 06 · NDA Triage
npx mcprush@latest skill add anthropics/nda-triage
# 07 · Contract Review
npx mcprush@latest skill add anthropics/contract-review
# 08 · SaaS / Subscription Agreement Review
npx mcprush@latest skill add anthropics/saas-subscription-agreement-review
# 09 · Compliance
npx mcprush@latest skill add anthropics/compliance
# 10 · Legal Risk Assessment
npx mcprush@latest skill add anthropics/legal-risk-assessment
# 11 · /renewal-tracker
npx mcprush@latest skill add anthropics/renewal-trackernpx).uvx, docs.astral.sh/uv).Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.Nothing is connected until you approve it in Claude Code. mcprush is not in the path and meters nothing here.
Installed together, these tool surfaces add up. It is the first thing a security reviewer asks for, so what has been counted — and what nobody has counted yet — is on the page rather than in a PDF.
| Member | Tool surface | Write tools |
|---|---|---|
| Word Mcp Live | imported | 91 |
| Courtlistener | not imported | not recorded |
| PandaDoc | not imported | not recorded |
A stack's blast radius is the union of its members, not the worst of them. That union cannot be taken here, because 2 members of 5 have no imported tool surface — so the figure a review asks for is missing rather than low, and a member marked not imported is one nobody has counted rather than one that cannot write.
A stack is a default, not a verdict. These are the substitutions the maintainer would make, and what each one costs or saves.
Without Microsoft Word installed, a server that edits the .docx file directly still reads the contract and its comments and writes changes — but not as live tracked changes.
Written by the maintainer, kept on the page rather than in a support thread.
It is not a lawyer and does not give legal advice. It prepares reviews and drafts for a qualified person to decide on.
It does not sign or send anything on its own. PandaDoc sends when a person tells it to, after the terms are approved.
Research covers US federal regulations, US case law in CourtListener and EU law in EUR-Lex. Other jurisdictions need their own sources.
A stack has an owner: whoever keeps it re-checks the combination when a member changes, and the members themselves are published by the people named on each row.
Tools to inspect code changes, run checks and prepare a pull request review.
Tools to investigate a bug report and work toward a reproducible test case.
Tools to investigate alerts, check recent changes and follow the runbook.