• TidioReply faster to tickets across all channels
  • LyroHire AI to handle customer servicecheck
  • Hubi AIRun on-brand marketing with an AI coworker
  • LabsTidio LabsGet a custom AI solution built by experts
  • Master AgentOrchestrates every channel
  • AI Voice AgentResolves calls on its own
  • Lyro for Zendesk
  • Lyro for Freshdesk
  • Lyro for Salesforce
  • Lyro for HubSpot
Browse all integrationsarrow_forward
  • Borrowell83% resolved
  • GameBoost86% automated
  • Cove Smart70% self-service
  • Secureframe59% automated
See all customer storiesarrow_forward
  • AI in E-Commerce in 2026Free report on the new shopping funnel
  • Shadow AIFree report on the hidden AI habit
  • AI in Insurance in 2026Free report on AI in insurance
See all reportsarrow_forward
  • Features
  • Pricing
Talk to salesGet started
Lyro wordmark

Product

  • Features
  • Master Agent
  • AI Voice Agent
  • Integrations
  • Pricing
  • Copilot

Resources

  • Blog
  • Customer Stories
  • Reports
  • AI in Ecommerce Report
  • Docs

Company

  • Contact
  • Book a Demo

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement

4.7/5on G2G2 logo

SOC 2 Type II · GDPR · CCPA

© 2026 Lyro by Tidio. All rights reserved.

Docparser

Docparser MCP integration

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

Connect DocparserSee all integrations

4actions available

  1. Home/
  2. Integrations/
  3. Docparser

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.

  • receipt_long

    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
  • task_alt

    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

What can you do in Docparser without me setting anything up?

These, right away:

  • Get multiple document results
  • Get parser models
  • List parsers

Great, let's start with the first one.

Ask Lyro anything...

FAQ

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.

  • Get Multiple Document Results returns up to 100 results by default and a maximum of 10,000, scoped to one parser. That is enough for Lyro to answer a question about a whole batch of documents rather than fetching them one at a time.

  • Because a Docparser parser can hold several layout models to cope with document variations. Get Parser Models lists them, so when a supplier's new invoice format comes back with empty fields Lyro can point at which layouts the parser actually covers.

  • Ping API is a credential and connection health check, so Lyro can confirm whether a failed lookup is an authentication problem rather than a missing document. If it cannot resolve the request, it hands the conversation to a human agent with the full history.

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.

The tools Docparser sits next to

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

  • Algodocsarrow_outward

    Algodocs

    Lists the extractors configured on an account with their IDs, returns the folder hierarchy, and confirms which AlgoDocs user the key belongs to.

  • Conversion toolsarrow_outward

    Conversion tools

    Uploads a file, runs the conversion, polls the task until it finishes, and returns the download link without anyone opening the dashboard.

  • Docupilotarrow_outward

    Docupilot

    Confirms the connected account, lists existing workspace folders, and creates the folder a set of generated documents should land in.

  • Extracta.aiarrow_outward

    Extracta.ai

    Configures extraction and classification jobs, retrieves batch results with their processing status, and clears jobs and credits down after.

  • One drivearrow_outward

    One drive

    Searches file contents for the document someone means, files attachments into the right folder, issues scoped sharing links, and restores deleted items.

  • Sanityarrow_outward

    Sanity

    Runs GROQ queries and fetches documents by ID, audits project roles and service accounts, and manages custom user attributes.

Browse every integration
Support agent working at a laptop next to the Lyro mascot

Ready to connect Docparser?

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

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