ClauseWise
Look up employment-law rule cards by jurisdiction and topic via a read-only MCP tool.
Query federal or state rules using
state("federal"or a two-letter code like"CA") andtopic(e.g.,release_timing,noncompete,confidentiality_whistleblower).Optionally filter by
as_of(YYYY-MM-DD); defaults to today and omits rules not yet effective on that date.Get matching rule cards with citations, effective dates, and plain-language summaries.
Receive the corpus version, "as of" date, and ClauseWise disclaimer (legal information, not legal advice).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ClauseWise review my NDA and explain the clauses that need attention"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ClauseWise
Open-source, MCP-native, state-aware contract explainer for employees and independent contractors. It reads the paper the stronger party handed you, flags the clauses that deserve attention, explains what each one does in plain language, and cites the relevant state or federal rule with a primary-source link and an "as of" date.
ClauseWise provides legal information and education, not legal advice. It does not tell you whether to sign, does not predict how a dispute would end, and is not a substitute for a qualified attorney licensed in your state.
See docs/PLAN.md for the full project plan and
docs/adr/ for the architecture decisions.
What it is
Jurisdictions: a federal overlay plus six priority states — California, New York, Texas, Washington, Illinois, Massachusetts.
Documents: NDAs, offer letters and employment agreements, separation/severance agreements, invention-assignment agreements (PIIAs), independent-contractor agreements, SOWs and payment terms.
Surface: one MCP server, shipped two ways — a local
stdiopackage (your LLM does the reasoning, the contract never leaves your machine except to the model you already use) and a remote Streamable HTTP endpoint (required for ChatGPT).
Related MCP server: Plain English
What it is not
Not a lawyer, not legal advice, not a prediction of how a dispute would end, and not a recommendation to sign or not sign. The product name and tagline never use the words "lawyer" or "attorney".
Repository layout
packages/core parsing, clause segmentation, schemas, retrieval, citation verification
packages/corpus versioned rule cards (YAML) + loader/lookup + snapshot build
packages/mcp FastMCP server (stdio + Streamable HTTP)
packages/evals Inspect AI tasks, legal-fact suite, golden sets, red-team
packages/monitor deterministic collectors + human-gated updater agent
packages/ft fine-tuning benchmark (QLoRA clause classifier)
site/ Astro landing pageQuickstart
Requires uv and Python 3.12 (uv will fetch it).
uv sync --all-packages # create the venv and install every workspace package
uv run ruff check . # lint
uv run pytest -q # unit + legal-fact tests
uv run clausewise-mcp # run the MCP server over stdio
uv run clausewise-mcp --http # run it over Streamable HTTP on :8000Register the local server with an MCP client
Claude Code — already wired up via .mcp.json at the repo root; approve the
server when prompted, then ask it to call lookup_rule.
Claude Desktop — add to claude_desktop_config.json:
{
"mcpServers": {
"clausewise": {
"command": "uv",
"args": ["run", "--directory", "/Users/carolyndriscoll/clausewise", "clausewise-mcp"]
}
}
}Status
Phase 1 in progress (California corpus + RAG). Built so far:
Corpus: 3 federal + 8 California rule cards (summary-level; verbatim statute text and exact effective dates are tracked for primary-source verification).
MCP tools (read-only):
lookup_rule,explain_clause,check_deadlines, plus guided prompts (review_severance/review_offer/review_nda/review_contractor_agreement) and theclausewise://corpus/manifestresource.Analysis primitives: clause segmentation, contract-type detection, a reversible redaction pre-pass, deterministic citation verification, and BM25 retrieval.
Evals: 53 legal-fact assertions; a retrieval eval harness (BM25 recall@5 0.973 on 37 worker questions).
Still ahead in Phase 1 (needs API keys): dense/hybrid retrieval + rerank, the single-pass
Claude analysis (analyze_contract → FlagReport), and the golden-contract flag evals. See
docs/PLAN.md §15.
uv run clausewise-retrieval-eval # print the retrieval metrics tableLicenses
Code: Apache-2.0 (see
LICENSE).Corpus plain-language summaries: CC BY 4.0.
Statute text: public domain.
Available Tools
1 toollookup_ruleLookup RuleA
Look up the employment-law rule card(s) for a state and topic.
Read-only. Returns the matching rule cards with citations, effective dates and a plain-language summary, plus the corpus version, the "as of" date and the ClauseWise disclaimer. This is legal information, not legal advice.
Inputs: state (required), topic (required), as_of. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of overlap or misselection between tools. The lone lookup_rule has a clearly stated purpose (state+topic rule card retrieval).
The single tool uses a clean, predictable verb_noun snake_case pattern (lookup_rule). With one tool there is no chance of inconsistent convention, though the sample is too small to demonstrate a real pattern.
A single read-only tool is very thin for a domain like employment-law rule lookup, which naturally suggests discovery, listing, and comparison operations. The surface feels under-scoped for the apparent purpose.
Only one read-only lookup exists; there is no way to list available states/topics, browse the corpus, search across rules, or retrieve citations separately. Agents hitting an unknown state or topic name have no fallback path, creating dead ends.
Related MCP Connectors
Contract review that keeps your contracts: cited answers, Word redlines, key-date alerts.
ContractOracle - 10 contract analysis tools: clause extraction, redlines, DORA mappings.
Contract drafting, statute-cited US state law requirements, non-compete checks, risk analysis.
Save reusable contract clauses, search them, and assemble a contract as .docx or markdown.
Related MCP Servers
- AlicenseAqualityDmaintenanceHelps AI agents author, validate, explain, draft, and test Liminate Agreements locally, with an optional API for translating compliance documents into Agreement drafts.6Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables users to paste contracts, leases, terms of service, and other documents to receive a plain-English summary of key risks, deadlines, rights, and negotiation points.MIT
- FlicenseNot gradedqualityDmaintenanceEnables extracting explicitly stated contract metadata, clauses, and obligations from user-supplied contract text without storing or modifying the data.-

EVIDIQ Clauseofficial
AlicenseNot gradedqualityBmaintenanceDecodes agreements and policy documents into plain language with verified citations, risk flags, obligation calendars, and comparisons, running in TEE-attested enclaves and producing cryptographically sealed, anchored reports.MIT