MCP server for LocalParse — accurate document parsing and schema-driven extraction for Cursor, Claude Desktop, and other MCP clients.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"localparse-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# localparse-mcp An [MCP](https://modelcontextprotocol.io) server that gives your coding agent (Cursor, Claude Desktop, etc.) **accurate document parsing** *and* **schema-driven JSON extraction** via [LocalParse](https://localparse.com) — table-detection recovery + arithmetic identity checks on the parse side, and a server-validated JSON Schema contract on the extract side — instead of letting it write throwaway OCR scripts. ## Tools ### Parse | Tool | What it does | |---|---| | `parse_document(path, result_type)` | Parse a local file (PDF/image/PPTX/…). | | `parse_url(url, result_type)` | Download a remote doc and parse it. | | `parse_folder(path, case_id, resume)` | Ingest a whole folder into a named case; re-runs only parse changed files. | | `get_structured(job_id)` | Fetch the structured ingestion contract for a job. | | `case_manifest(case_id)` | List a case's ingested docs (path + hash + status). | | `case_failures(case_id)` | List a case's failed docs for reingest. | `result_type` ∈ `markdown` (default), `text`, `json`, `structured`. ### Extract *(Beta)* | Tool | What it does | |---|---| | `extract_document(path, data_schema, system_prompt?)` | Parse a file **and** extract structured JSON in one call. Most useful tool for agents. | | `extract(markdown, data_schema, system_prompt?)` | Run the extract step on already-parsed markdown. | The server validates the model's output against your `data_schema` before returning, so the JSON you get back is guaranteed to match the shape you asked for. Example natural-language prompts an agent can use: > *"Use `extract_document` on `./invoices/q3.pdf` with this schema: > `{type:'object', properties:{vendor:{type:'string'}, total:{type:'number'}}, required:['vendor','total']}`"* ## Configure your client You need a LocalParse API key (`LOCALPARSE_API_KEY`). ### Cursor — `~/.cursor/mcp.json` (or project `.cursor/mcp.json`) ```json { "mcpServers": { "localparse": { "command": "uvx", "args": ["l…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.