Day 9 — AI Engineering / Legal
Hand it a contract. Get back: parties, key dates, obligations, red flags.
An MCP server that turns a stack of legal documents into a queryable knowledge base. Ask about any contract in plain English — no more ctrl+F through 30-page PDFs.
Example Queries
Tools
| Tool | What It Does |
|---|---|
| document_search | Search and browse contracts by title, type (MSA, NDA, lease, etc.), or status |
| party_lookup | Find parties across all documents — names, roles, entity types, and contact info |
| key_dates_tracker | Track deadlines, expirations, and renewal dates — flags overdue items |
| obligation_tracker | Party obligations grouped by document — payment terms, compliance, restrictions |
| clause_analyzer | Analyze clauses across documents — termination, IP, non-compete — with risk levels |
| red_flags | Surface risks and red flags — severity-ranked with section refs and recommendations |
Why This Build
Every company has a drawer full of contracts they signed but never read again. The lease auto-renewed. The non-compete is unenforceable. The vendor agreement expired three months ago.
Legal teams charge $500/hour to read these. Paralegals spend days building clause comparison spreadsheets. Meanwhile, the CEO asks “when does our office lease expire?” and nobody knows without digging.
This is the first AI Engineering build in the challenge. Same MCP pattern, but the value proposition shifts from “query your data” to “understand your documents.”
Demo Data
10
Documents
20
Parties
31
Key Dates
26
Obligations
25
Clauses
14
Red Flags
10 realistic legal documents for a mid-size digital agency: MSA, NDA, commercial lease, software license, employment agreement, contractor agreement, partnership, vendor contract, settlement, and a DPA under review. Includes edge cases — an expired vendor contract, a settlement with payment deadlines, an auto-renewing license with an 8% increase, and a non-compete that may not be enforceable in California.
Setup
cd day09-document-analyzer
npm install && npm run seed && npm run buildThen add the config to Claude Desktop and restart.
If your team spends more time searching for answers in documents than acting on them, let's build something better.