Docparser

Docparser MCP integration

Pulls parsed field data for a batch of documents, lists parsers and their layout models, and verifies the API connection.

4actions available

Three actions you can hand over today

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

  • Get multiple document results

    Lyro retrieves parsed data from documents already processed by a parser to extract key information. Results are structured and ready for immediate use or storage.

  • Get parser models

    Lyro fetches all model layouts configured for a parser to understand available parsing patterns. Model details inform customization and field-mapping strategies.

  • List parsers

    Lyro displays all available document parsers to help customers select the optimal parser for their document type. Parser descriptions include supported formats and use cases.

See all 4 actions

How businesses use Docparser + Lyro

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

  • Read the fields extracted from a batch of documents

    Lyro finds the right parser on the account and pulls the parsed results for many documents at once, so a question about invoice totals or reference numbers is answered from extracted data.

    List ParsersGet Multiple Document Results
  • Check the parser setup when a result looks wrong

    Lyro lists the layout models inside a parser that handle document variations and verifies that the API credentials still authenticate, separating a configuration gap from a connection problem.

    Get Parser ModelsPing API

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 Docparser actions it has and picks the ones a request needs.

  1. 01

    Connect Docparser

    Authorize the Docparser 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 Docparser 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
Docparser · Lyro

Everything else about Docparser

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

  • No. All four actions read: Get Multiple Document Results, Get Parser Models, List Parsers and Ping API. Documents keep reaching Docparser the way they do today, and Lyro works with the parsed output once the parser has run.

Every action available in Docparser

All 4 actions your agent can call on Docparser, straight from the live MCP connection.

  • Get multiple document results

    Retrieve parsed data from multiple documents processed by a specific parser.

  • Get parser models

    Retrieve all model layouts for a specific parser.

  • List parsers

    Retrieve all Document Parsers linked to your account.

  • Ping API

    Test API authentication and connection health check for Docparser API.

Ready to connect Docparser?

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

Support agent working at a laptop next to the Lyro mascot