Legal Doc Analyzer MCP server
Domain-specific MCP tooling for legal document workflows
not scanned yet
1 stars
Reviews
Write oneNobody has reviewed Legal Doc Analyzer yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Legal Doc Analyzer tools
No tool declarations could be read from the package source. They show once the server is installed.
How Legal Doc Analyzer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
Release history: 2 versions in the registry since 2026-03-23, latest 2026-11-04, typically one every 225 days.
Install Legal Doc Analyzer in Claude Code, Cursor or VS Code
Runs npx -y mcp-legal-doc-analyzer on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-legal-doc-analyzer -- npx -y mcp-legal-doc-analyzer
What the publisher says
From the Legal Doc Analyzer repository's README, as published. We do not edit it. Read it on GitHub
MCP Legal Document Analyzer
npm mcp-legal-doc-analyzer package
Domain-specific MCP tooling for legal document workflows. Extract key clauses from contracts, flag risky provisions against configurable rule templates, compare document versions at the clause level, and check compliance against standard checklists — all locally, without documents leaving your machine.
Tool reference | Configuration | Contributing | Troubleshooting
Key features
- Clause extraction: Identifies and labels clause boundaries (termination, liability, IP, governing law, and more) from PDF, DOCX, and plain-text files.
- Risk flagging: Checks extracted clauses against YAML rule templates and returns severity-ranked findings.
- Compliance checking: Validates documents against structured checklists (NDA, employment agreement, SaaS terms) with pass/fail per requirement.
- Version diffing: Compares two versions of a document at the clause level — not raw text lines.
- Configurable templates: Rule sets are YAML files that legal professionals can review and edit without writing code.
- Local-only processing: All parsing and analysis runs on-device; documents are never transmitted externally.
Disclaimers
mcp-legal-doc-analyzer is an analysis aid, not legal advice. Outputs should be reviewed by a qualified legal professional before making decisions. Clause extraction uses pattern matching and heuristics; results may be incomplete or incorrect for non-standard document formats. Low-confidence extractions are flagged explicitly.
Document contents are processed locally and stored in a local SQLite database. Do not share database exports containing confidential documents.
Requirements
- Node.js v20.19 or newer.
- npm.
Getting started
Add the following config to your MCP client:
{
"mcpServers": {
"legal-analyzer": {
"command": "npx",
"args": ["-y", "mcp-legal-doc-analyzer@latest"]
}
}
}To load custom compliance templates from a directory:
{
"mcpServers": {
"legal-analyzer": {
"command": "npx",
"args": ["-y", "mcp-legal-doc-analyzer@latest", "--templates=~/legal/my-templates"]
}
}
}MCP Client configuration
Amp · Claude Code · Cline · Cursor · VS Code · Windsurf · Zed
Your first prompt
Provide a PDF or DOCX contract file, then enter:
Extract the key clauses from this NDA and flag any risky provisions.Your client should return a list of extracted clauses and a risk report ranked by severity.
Tools
Document analysis (4 tools)
- extract_clauses — identify and label clause boundaries with confidence scores; supports .pdf, .docx, .txt
- flag_risks — severity-ranked risk findings against a compliance template
- check_compliance — structured pass/fail checklist validation per rule
- summarize_terms — plain-English bullet-point summary of key provisions
Comparison (1 tool)
- compare_versions — clause-level diff between two document versions
Templates (1 tool)
- list_templates — enumerate all available compliance templates
Export & bulk (3 tools)
- exportanalysisreport — self-contained HTML report with clause table and risk findings; suitable for printing
- exportauditlog — export the analysis audit log in JSON or CSV format with optional date-range filtering
- bulk_analyze — process a portfolio of contract files in batch with progress notifications
Bundled templates
Nine compliance templates are included out of the box:
- NDA
- Employment Agreement
- SaaS Customer Agreement
- Software License Agreement
- Vendor Agreement
- Consulting Agreement
- Data Processing Agreement
- IP Assignment
- Loan Agreement
Use list_templates to enumerate all available templates at runtime, including any custom templates loaded via --templates.
Configuration
--templates / --templates-dir
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Legal Doc Analyzer: common questions
- Is Legal Doc Analyzer MCP server safe?
- Mostly: it is graded B (83/100). Read the Legal Doc Analyzer safety report
- How do I install Legal Doc Analyzer?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Legal Doc Analyzer need an API key?
- Yes. The registry entry asks for
YOUR_API_KEY. - Is Legal Doc Analyzer maintained?
- The last commit was 43 days ago (2026-09-22). The latest release is v1.0.1.
- How does Legal Doc Analyzer compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.