Parserail Mcp
tech.thecompoundPublished by thecompound.techv0.6.2Updated Nov 7, 2026
Documents to schema-valid JSON plus 38 more finished-job AI tools, on one credit wallet.
Overview
A local MCP server that turns documents into schema-valid JSON and offers 38 more finished-job AI tools, billed from one prepaid credit wallet.
- What you can do
- Convert documents into schema-valid JSON output through the ParseRail service, using a single API key and credit wallet for all calls. Access a set of 38 additional finished-job AI tools alongside the document parsing, all drawn from the same account. The manifest does not list individual tools, so the exact operations are not documented here.
- When to use it
- Useful when an assistant needs to extract structured, schema-valid JSON from documents, or to reach ParseRail's other finished-job AI tools without building that pipeline yourself.
- Requirements
- Runs as a local process over stdio, installed from the npm package parserail-mcp, so Node.js is needed. Requires a ParseRail API key supplied in the PARSERAIL_API_KEY environment variable, obtained from the ParseRail dashboard. Desktop only; no free tier.
Installation
In SourceWeft
- Open Parserail Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
4- v0.6.2LatestOct 16, 2026
- v0.6.0Oct 15, 2026
- v0.5.8Oct 2, 2026
- v0.5.5Sep 19, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.