DocuPipe

io.github.DocuPipePublished by GitHub account DocuPipev0.1.0Updated Nov 7, 2026

Upload documents and extract structured JSON from Claude Code, Codex, Cursor and other MCP clients.

VerifiedSTDIODesktop onlyFiles & StorageData & Analytics

Overview

AI-generated overview

DocuPipe MCP server lets an assistant upload documents and extract structured JSON fields from them using saved or inline schemas.

What you can do
  • Upload local files or URLs and wait for them to be read
  • Inspect a document's status, page count and parsed text
  • Extract structured JSON with a saved schema, an inline JSON Schema or a drafted one, and fetch results
  • Create and list schemas, classify documents into account classes
  • Split files into sub-documents and convert documents to Excel workbooks
  • Run saved workflows and check or wait on jobs
When to use it
Useful when you want an agent to pull named fields out of invoices, forms or other PDFs in bulk and save the results as JSON, or to turn documents into spreadsheets without defining a schema first.
Requirements
Runs locally over stdio via npx, so Node.js 18 or newer is needed. A DocuPipe account and API key are required, passed as the DOCUPIPE_API_KEY environment variable; DOCUPIPE_BASE_URL optionally overrides the API address. Network access to the DocuPipe API is required.
Before you install
The API key is a secret stored in the client's MCP configuration. Documents and URLs are sent to the DocuPipe service for processing, so avoid confidential files unless that is acceptable. Tools create schemas, upload documents, run workflows and write result files (including a docupipe-results folder) in the directory the server was started in.

Installation

In SourceWeft

  1. Open DocuPipe in the dashboard and add it to a workspace.
  2. 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

DocuPipe MCP server

Use DocuPipe from Claude Code, Codex, Cursor and other MCP clients. Ask your agent to "pull the line items out of these invoices" and it uploads the files, extracts the fields you named and saves the JSON, in one tool call per file.

Setup

  1. Sign up and copy your API key from the Developers card on the Settings page.
  2. Add the server to your client, replacing your-api-key. Node.js 18 or newer is required.

Claude Code

bash
claude mcp add docupipe --scope user -e DOCUPIPE_API_KEY=your-api-key -- npx -y @docupipe/mcp

Codex

bash
codex mcp add docupipe --env DOCUPIPE_API_KEY=your-api-key -- npx -y @docupipe/mcp

Cursor: open this link to install, then replace your-api-key in Cursor's MCP settings:

cursor://anysphere.cursor-deeplink/mcp/install?name=docupipe&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBkb2N1cGlwZS9tY3AiXSwiZW52Ijp7IkRPQ1VQSVBFX0FQSV9LRVkiOiJ5b3VyLWFwaS1rZXkifX0=

Or add it by hand. Cursor and other clients that use an mcp.json file:

json
{  "mcpServers": {    "docupipe": {      "command": "npx",      "args": ["-y", "@docupipe/mcp"],      "env": { "DOCUPIPE_API_KEY": "your-api-key" }    }  }}

Then ask, for example:

Use DocuPipe to extract the invoice number, date, vendor and line items from every PDF in ./invoices and save one JSON file per invoice.

Tools

ToolWhat it does
extractFile or URL in, structured JSON out: uploads, extracts with a saved schema, an inline JSON Schema or a schema DocuPipe drafts, waits, and can save the result
upload_documentUpload a local file or URL and wait for it to be read
get_documentStatus, page count and parsed text of a document
standardizeExtract from an already uploaded document
get_standardizationFetch an extraction result
create_schema, list_schemasSave a JSON Schema, or reuse one the account already has
list_classes, classifyClassify a document into the account's classes
split_documentSplit a file into sub-documents, with AI choosing where each one starts
list_workflows, run_workflowRun a saved workflow on a file
convert_to_excel, get_excel_conversionTurn a document into an .xlsx workbook without a schema, and save it locally
get_job, wait_for_jobsCheck or wait on any job

Each call returns within about 45 seconds. When DocuPipe needs longer, the tool returns status: "processing" with every id created so far and the exact call to resume with. Resuming never uploads or extracts a second time.

Credits

Tools use credits from your DocuPipe account. Upload is 1 credit per page for PDF, image, Word and HTML files (CSV, Excel, JSON, text and XML are free to upload). Extraction is 2 credits per page at standard effort and 4 at high effort. See credits and billing for every operation.

Configuration

Variable
DOCUPIPE_API_KEYRequired. Your API key.
DOCUPIPE_BASE_URLOptional. Overrides the API address. Defaults to https://app.docupipe.ai.

Relative file paths resolve against the directory the server was started in, which for most clients is your project folder. Local files up to 100 MB are supported; pass a URL for larger files. Results larger than about 40,000 characters are written to docupipe-results/ in that folder and the tool returns the path with a preview.

Links

License

MIT

Source: README.md at commit c803502

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 7, 2026

Score

50% 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
  • License10 pts