Does this tool parse the document directly or use the cloud engine?

The tool offloads the logic specifically via endpoints mapping back to the Parseur Cloud Engine. The AI acts to organize mailboxes, list templates, and fetch final states securely without computing massive local OCR networks.

Can I upload a raw file string to be parsed?

Yes. Utilizing the explicitly mapped `upload_document` constraint, the agent can inject raw string boundaries identifying formatting, passing files straightforward into the target mailbox ID natively.

Will I see missing required fields if extraction fails?

Absolutely. Querying `get_document_details` lists specific status bounds. If a template expects InvoiceTotal and misses it, the document flags a processing boundary issue precisely traceable here.

Parseur MCP Connector for Claude

A+

Automate document processing via Parseur — list mailboxes, upload PDFs/Emails, extract structured data pipelines, and trigger template logic natively.

10 tools Official Updated Jun 28, 2026 Official Vinkius Partner

More Details Connect to Claude

Bring Parseur Document Extraction arrays directly into your AI workflows. By explicitly mapping into powerful OCR and templating engines, your agent can push unstructured PDFs or bulk emails into remote routing limits, parsing exact text fields securely. Extract fields, examine documents, list defined parse-templates, and retry pipelines without manual intervention.

What you can do

Mailboxes & Templates — Examine specifically bound mailboxes tracking which explicit templates dictate data extraction limits mapped natively
Document Navigation — Extract properties showing precisely which unstructured strings were identified inside uploaded payloads checking status: parsed correctly
Payload Uploading — Instruct the node limits mapping upload_document generating raw payloads routing straight into the engine for OCR logic
Job Management — Discover disconnected states mitigating failed validations by pushing retry_document instantly forcing physical pipeline resets

How it works

Subscribe to this server
Enter your Parseur API Key explicitly
Start evaluating explicit AI OCR workflows reliably via Claude, Cursor, or any MCP structure

Who is this for?

Operational Workflows — explicitly map invoicing pipelines investigating extraction errors remotely avoiding web limits
Finance Teams — trace OCR receipts dynamically identifying missing fields from Chat architectures directly into a JSON limit natively
Developers — route manual document loads simulating continuous AI logic mapping testing integrations on webhook bounds

ocrdata-parsingemail-automationpdf-processingtemplate-extractionstructured-data

10 tools expose this connector's capabilities to your AI agent.

create_mailbox

The type determines the parsing engine (e.g., "pdf", "email", "attachment"). Once created, you can configure templates and forward documents to the mailbox for automatic extraction. Create a new Parseur mailbox for document parsing

create_template

Pass the template name and a JSON config string defining field mappings. Parseur will use this template to extract structured data from matching documents. Create a new extraction template for a Parseur mailbox

get_document_data

Fields depend on the template configuration (e.g., invoice_number, total_amount, line_items). Only works for documents with status "processed". Retrieve the fully extracted JSON data from a parsed document

get_document_details

Does not include the parsed data itself — use get_document_data for that. Get metadata of a single parsed document

get_mailbox

Use this to verify mailbox setup before sending documents. Get detailed configuration of a specific Parseur mailbox

list_documents

Each entry includes document ID, status (processed, failed, pending), and metadata like sender and received date. List all parsed documents inside a Parseur mailbox

list_mailboxes

Each mailbox represents a parsing pipeline for a specific document type (invoices, receipts, emails). Use the returned mailbox IDs for subsequent operations like listing documents or uploading files. List all Parseur parsing mailboxes

list_templates

Templates define the extraction rules (field names, locations, regex patterns) used to pull structured data from incoming documents. List available extraction templates for a Parseur mailbox

retry_document

Useful after fixing template rules or when the original parse failed due to a transient error. The document will be matched against the latest template rules. Retry parsing a failed or errored Parseur document

upload_document

eml) to the specified mailbox for automatic parsing. The document enters the processing queue and will be parsed according to the mailbox template. Returns the new document ID for tracking. Upload a document URL to a Parseur mailbox for parsing