Document To JSON MCP Server

Connect Document To JSON to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Turn any PDF into structured JSON via AI + OCR: invoices, bank statements, contracts. The document to json mcp server is what makes that connection.

What the server does

Perfect for: - Accountants — extract invoice data (numbers, dates, totals, VAT, IBAN) - Developers — automate document processing in your apps - Business analysts — convert bank statements to spreadsheets - Legal teams — extract contract clauses and dates automatically

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: YOUR_APIFY_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by fashionmascherine-svg; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.