Suparse Document Processing MCP Server

MCP stdio server for the Suparse Document Processing API. Use it from local MCP clients such as Claude Code and Codex to extract structured data from documents into JSON, CSV, XLSX, or Google…

Local serverstdioMIT

What is the Suparse Document Processing MCP Server?

Suparse is an MCP project maintained in the suparse/suparse-mcp repository. The maintainer describes its purpose as “MCP stdio server for the Suparse Document Processing API. Use it from local MCP clients such as Claude Code and Codex to extract structured data…”. Read the project documentation for the complete scope.

Installation

The documented npm package is @suparse/mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.

Configuration values

The example declares SUPARSE_API_KEY. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
extract_fileProcess one local document. Defaults to result_mode: "defer", returning compact task_id/document_ids metadata for later download_results. Use result_mode…
extract_folderProcess supported files in one local folder. Defaults to result_mode: "defer", returning compact task_id/document_ids metadata for later download_results.…
list_templatesList summary or full template records, grouped into directly usable team_templates and discovery-only system_templates.
start_quick_schema_creationStart automatic schema creation for one local document and return a normalized run ID.
get_quick_schema_creationFetch the current automatic schema creation status for a run ID.
wait_for_quick_schema_creationPoll automatic schema creation until it reaches a terminal result.
fetch_json_resultsFetch JSON extraction results by document ID directly in the MCP response. Use only when full JSON is needed in context.
fetch_document_resultFetch one document's structured JSON result through the direct single-document endpoint.
download_resultsFetch an export by document ID and write it directly to local disk. Use this for json, csv, xlsx, and google_sheets.
delete_documentsDelete documents by ID.
export_typeoriginal, unified

How to install the Suparse Document Processing MCP Server

{
  "mcpServers": {
    "suparse": {
      "command": "npx",
      "args": [
        "-y",
        "@suparse/mcp"
      ],
      "env": {
        "SUPARSE_API_KEY": "YOUR_SUPARSE_API_KEY"
      }
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

VariableDescriptionRequired
SUPARSE_API_KEYDeclared in the maintainer’s client configuration.Check documentation