Parseur

Parseur MCP integration

Sends documents in for parsing, explains why one came back stuck, reprocesses a batch after a template change, and routes the parsed data onward.

Connect ParseurSee all integrations

26actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Upload email document

    Lyro uploads an email or text document to Parseur for parsing. Support processes customer documents and extracts structured data automatically.

  • Get document

    Lyro fetches full details of a parsed document from Parseur. Support confirms extraction succeeded and reviews the results with customers.

  • Reprocess a document

    Lyro reprocesses a document in Parseur after template fixes. Support recovers failed extractions without requiring customers to upload again.

See all 26 actions

How businesses use Parseur + Lyro

Each card is one request a support team gets, and the Parseur actions Lyro runs to close it.

  • Send a document in and read the fields back

    Lyro uploads the email or text document to the right mailbox, retrieves it once processed with its parsed results and JSON, CSV, and XLS download URLs, and checks the schema those fields follow.

    Upload Email DocumentGet DocumentGet Mailbox Schema

  • Explain why a document did not parse

    Lyro reads the processing logs on a document with each entry's status, source, and message, checks which templates the mailbox had to match against, and skips the one that was never going to parse.

    Get Document LogsList Templates for MailboxSkip a Document

  • Reprocess a batch after a template change

    Once a template is updated, Lyro lists the documents in the mailbox, re-parses the ones that failed against the new configuration, and copies a document to another mailbox when it landed in the wrong parser.

    List Documents in MailboxReprocess a DocumentCopy Document

  • Route parsed data where it needs to go

    Lyro enables a paused webhook so document.processed events start firing again, changes its target URL or event type, and defines the CSV or XLS export listing exactly which fields leave the mailbox.

    Enable WebhookUpdate WebhookCreate Custom Download

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Parseur actions it has and picks the ones a request needs.

  1. 01

    Connect Parseur

    Authorize the Parseur account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Parseur actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free
Parseur · Lyro

Everything else about Parseur

Setup, permissions, and the limits of what Lyro can do inside Parseur.

  • Because only paused webhooks can be enabled. Enable Webhook works on entries in available_webhook_set; once enabled the webhook moves into webhook_set and starts POSTing to its target URL when its configured event fires, such as document.processed. Disable Webhook moves it back the other way.

Every action available in Parseur

All 26 actions your agent can call on Parseur, straight from the live MCP connection.

  • Copy document

    Copy a document to another mailbox.

  • Copy mailbox

    Copy a mailbox (parser) in Parseur.

  • Create custom download

    Create a custom download (export configuration) for a mailbox.

  • Create mailbox

    Create a new mailbox (parser) in Parseur.

  • Delete custom download

    Delete a custom download (export configuration) from a mailbox.

  • Delete document

    Delete a specific document by ID.

  • Delete mailbox

    Delete a mailbox (parser) by ID.

  • Delete webhook

    Delete a specific webhook.

  • Disable webhook

    Disable a webhook for a mailbox.

  • Enable webhook

    Enables a paused webhook for a specified mailbox, allowing it to receive and forward parsed document events.

  • Get bootstrap config

    Retrieve bootstrap configuration data.

  • Get document

    Retrieve full details of a specific document by ID.

  • Get document logs

    Get document logs for a specific document.

  • Get mailbox by ID

    Retrieve full mailbox (parser) configuration by ID.

  • Get mailbox schema

    Retrieve the JSON schema for a mailbox's parsed fields.

  • List custom downloads

    Retrieve custom downloads (export configurations) for a mailbox.

  • List documents in mailbox

    List documents within a specific mailbox.

  • List mailboxes (full details)

    List mailboxes (parsers) with full configuration details.

  • List templates for mailbox

    List all templates in a given mailbox.

  • Reprocess a document

    Reprocess a document.

  • Retrieve a webhook

    Retrieve details of a specific webhook.

  • Skip a document

    Skip a document.

  • Update custom download

    Update a custom download (export configuration) for a mailbox.

  • Update mailbox

    Update a mailbox (parser) configuration.

  • Update webhook

    Update an existing webhook’s settings.

  • Upload email document

    Upload an email or text document to Parseur for parsing.

The tools Parseur sits next to

Same connection, same setup. Pick the next one your team already uses.

Browse every integration

Ready to connect Parseur?

Authorize the account and your agent has all 26 actions from the first conversation.

Connect ParseurTalk to sales
Support agent working at a laptop next to the Lyro mascot