← All integrations

Docparser MCP server

10 operations0 webhooks

Send documents to Docparser parsers and read the data they extract (invoices, orders, bank statements, forms).

Try Docparser with your agent

Connect Docparser, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Docparser on my account, then run one read-only example and show me the result.

Runs once, when you ask

Docparser tools and triggers

Tools are what your agent can do in Docparser through Corsair's MCP server. Triggers are the Docparser events a routine can start from.

Documents

  • FetchDestructive

    Import a document from a public URL into a parser. Uses parsing credits (one per 5 pages). Parsing takes a few minutes; check documents.status, then read results.get.

    documents.fetch

  • ReintegrateDestructive

    Send documents' parsed data to the parser's integrations and webhooks again.

    documents.reintegrate

  • ReparseDestructive

    Parse documents again with the parser's current rules, replacing their parsed data. Uses no extra credits.

    documents.reparse

  • StatusRead-only

    Check whether a document has been imported and parsed (done), and list any failed jobs.

    documents.status

  • UploadDestructive

    Upload a base64-encoded document into a parser. Uses parsing credits (one per 5 pages). Parsing takes a few minutes; check documents.status, then read results.get.

    documents.upload

Results

  • GetRead-only

    Get the parsed data of one document.

    results.get

  • ListRead-only

    Get the parsed data of a parser's documents, newest first (100 by default). Filter by upload or processing date or remote id. Each row holds the fields the parser extracted.

    results.list

Models

  • ListRead-only

    List the model layouts of one parser.

    models.list

Parsers

  • ListRead-only

    List document parsers (id and label).

    parsers.list

Ping

  • PingRead-only

    Check that the API key is accepted.

    ping

Connect Docparser to Claude, ChatGPT or Cursor

  1. 1

    Connect Docparser in Corsair

    Add your Docparser API key once in Corsair. Corsair stores the credential encrypted and makes the Docparser API calls for your agent, so it never goes into a prompt or a config file. Connect Docparser

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Docparser. On a ChatGPT personal plan, connect Docparser here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Docparser's read and write operations run right away and its 4 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/docparser, add the Docparser plugin, and connect with an API key. Then call methods like corsair.docparser.api.documents.fetch() from your app. Corsair syncs data per tenant.

Yes. Docparser requires an API key from your Docparser account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Docparser, GitHub, Notion, Stripe, and the rest. Trigger Docparser from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for send documents to Docparser parsers and read the data they extract (invoices, orders, bank statements, forms). Common builds include sync jobs, admin tooling, and agents that call Docparser APIs from your backend. Local DB entities let you query synced Docparser records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Docparser API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/docparser in the open repo. When Docparser ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Docparser data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Docparser data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Docparser on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 4 destructive Docparser operations. You can change a link's mode at hub.corsair.dev/me.