mcp-legal-doc-analyzer
by dbsectrainer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB | No | Path to the SQLite database file used to store document analysis history. | ~/.mcp/legal.db |
| OCR | No | Enable OCR fallback for scanned PDFs that contain no extractable text layer. Requires the optional peer dependencies tesseract.js, pdfjs-dist, and canvas. | false |
| HTTP_PORT | No | Start the server in Streamable HTTP mode on the given port instead of stdio. | |
| TEMPLATES | No | Directory to load custom YAML compliance rule templates from. Templates in this directory are merged with the built-in set. | |
| NO_HISTORY | No | Disable storing document analysis results in the local database. | false |
| CLAUSE_PATTERNS | No | Path to a YAML file defining custom clause detection patterns. | |
| BULK_CONCURRENCY | No | Number of files to process in parallel when using bulk_analyze. | 4 |
| CONFIDENCE_THRESHOLD | No | Minimum confidence score (0–1) for extracted clauses to be included in results. Extractions below this threshold are flagged as low-confidence. | 0.6 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessNo issues