A production-grade Model Context Protocol server for any caseworked, deadline-driven, document-heavy practice. Choose a domain pack — legal, accounting, claims, compliance — and the engine drafts, files, extracts, routes, reminds, and verifies across your systems, with mandatory human-in-the-loop gates, tamper-evident audit logging, and a fail-closed confidentiality gate.
The Case Automation MCP Server exposes every major operational workflow as a typed, auditable, reversible operation. The engine is domain-agnostic: terminology, case types, deadline rules, document classes, and the confidentiality policy live in a swappable domain pack, so the same hardened core serves a US immigration practice (the reference pack) just as readily as an accounting, claims, or compliance shop. Connect your systems — or use the included reference adapters — and let AI agents draft, file, extract, route, remind, and verify across every tab.
Turn a lead email or form into a structured matter + CRM contact + opening task list in under 10 minutes.
Detect matter status changes, draft on-brand updates, and route them for one-click human approval before sending.
Fill templates from matter data, output DOCX/PDF, version and store back — with gap placeholders for missing fields.
Auto-classify, name, file, and permission documents to the correct matter folder — with a non-overridable, pack-configurable confidentiality gate (privilege, client-confidential, restricted).
Compute business-day deadlines from rule sets, arm redundant reminders, and escalate on slippage — never silent-fail.
Run 7 composable checks — completeness, consistency, confidentiality, attachment integrity — before anything external leaves.
Swap the practice without touching the engine. A domain pack bundles terminology, case types, deadline rules, document classes, and the confidentiality policy. Immigration ships as the reference pack.
Every external or irreversible action is blocked behind a human-approval gate. Every state change writes to a tamper-evident hash-chained audit log before completion. Everything domain-specific — what a case is called, which deadlines apply, what counts as confidential — comes from the active domain pack, never from the engine.
The architecture was built domain-agnostic from day one — the core types (Matter, Contact, Document, Deadline) carry no domain semantics. A domain pack supplies everything practice-specific and is loaded at startup; the engine's mechanics never change.
| The engine provides (fixed) | The domain pack supplies (swappable) |
|---|---|
| Workflow orchestration, gates, idempotency | Terminology (Matter / Case / Engagement / Claim) |
| Hash-chained audit, crypto, RBAC mechanics | Case types + opening task checklists |
| Business-day math, reminders, escalation | Deadline rule sets |
| Fail-closed confidentiality gate, PII floor | Confidentiality label + document classes |
| Connector ports + webhook ingestion | RBAC roles + PII pattern additions |
Two safety guarantees are engine-owned and a pack can only tighten, never weaken: the confidentiality gate (no restricted document reaches an external recipient — fail-closed, never warns) and the PII redaction floor (a pack may add patterns, never remove the baseline). An incomplete or safety-weakening pack is rejected at load. See Domain Packs.
| Dimension | Score |
|---|---|
| Security | 96 / 100 |
| Architecture | 93 / 100 |
| Test quality | 93 / 100 |
| Code correctness | 98 / 100 |
| Documentation | 94 / 100 |
| CI/CD | 92 / 100 |
| Maintainability | 90 / 100 |
| Production readiness | 82 / 100 |
Overall: 91 / 100 — Grade A−
Last updated: 2026-06-25