Day 10 — AI Engineering / Legal & Consulting
Every consulting firm has the same problem: onboarding takes 3 meetings when it should take 1.
An MCP server that manages the entire client intake pipeline — from first contact through conflict checks, engagement letters, document collection, and kickoff.
Example Queries
Tools
| Tool | What It Does |
|---|---|
| client_search | Search clients at any intake stage — prospects, in-progress, onboarded, declined, or withdrawn |
| intake_review | Review intake forms with full data, flags, and approval status. Surface forms needing attention |
| conflict_checker | Run conflict of interest checks — pending, found, confirmed. Critical for ethics compliance |
| engagement_tracker | Track engagement letters — drafts, sent, signed. Fee structures, retainers, and expiration dates |
| workflow_status | Intake workflow progress per client — completed, in-progress, blocked, overdue steps with progress bars |
| document_tracker | Track collected documents — uploaded files, review status, and flags for each client |
Why This Build
Client intake at law firms and consulting agencies is a mess of email threads, shared drives, and “did anyone run the conflict check?” conversations. A single missed step can mean ethical violations, malpractice exposure, or simply a terrible first impression.
Most firms use a spreadsheet or a half-implemented CRM. The intake coordinator keeps the real process in their head. When they're out sick, everything stalls.
This tool makes the invisible workflow visible. Every client has a clear pipeline from prospect to onboarded, with conflict checks that actually get flagged and engagement letters that don't expire in a drawer.
Demo Data
12
Clients
8
Intake Forms
8
Conflict Checks
6
Engagements
40
Workflow Steps
15
Documents
12 clients across 7 practice areas at different stages: 3 fully onboarded, 4 in-progress (including one blocked by a conflict), 3 new prospects, and 2 declined/withdrawn. Includes a real conflict of interest scenario, an engagement letter approaching expiration, flagged environmental documents, and overdue workflow steps.
Setup
cd day10-client-intake
npm install && npm run seed && npm run buildThen add the config to Claude Desktop and restart.
If your intake process lives in someone's head instead of a system, let's fix that.