Skip to main content

Overview

ADP MCP Server is the Model Context Protocol server for Laiye ADP. It lets MCP-compatible AI clients, such as Claude Desktop, Cursor, Copilot Chat, Tongyi Lingma, and Coze, call ADP document parsing and extraction without writing code. Unlike the CLI, MCP Server runs over Streamable HTTP. A single connection can discover available tools, submit processing tasks, and query results inside the chat window. ADP combines vision language models, large language models, and agentic decision-making. It upgrades rule-driven field extraction into goal-driven document automation. ADP can classify and extract key fields from invoices, domestic bills, purchase contracts, logistics documents, financial reports, transaction contracts, and more. It supports table parsing, content verification, and multilingual recognition without manual templates, labeled data, or rule maintenance.

Try ADP

Sign up for ADP. New users receive 100 free credits each month.

Quick start

1. Get an API key

Visit adp-global.laiye.com, register an ADP account, and get your API key from My MCP in personal settings.

2. Configure your MCP client

For private deployments, replace the domain with your actual service address.

3. Start using ADP

After connection, the AI client discovers all available ADP tools. Describe your task in chat, for example:
  • “Parse the structure of this PDF.”
  • “Extract information from this ID card.”
  • “Extract amount and date from this invoice.”

Tools

Document parsing

Bills and order extraction

Cards and certificates

Custom extraction

MCP also provides two tools for custom extraction applications created in the ADP platform:
First call list_custom_extract_apps to find the target app_id, then call execute_custom_extract_app with the file and app_id.

Tool input parameters

Document parsing and OOTB extraction tools

All out-of-the-box tools share the same input schema:

execute_custom_extract_app

This tool also requires:
File input: Values starting with http://, https://, or file:// are treated as URLs. Other values are treated as Base64 content.Sync vs async: wait=true blocks until processing completes. wait=false returns task_id immediately for later querying.

Tool output

parse_document output

Extraction tool output

Normal fields: Table fields:
If a field object contains table_values, it is a table field. If it only contains field_values, it is a normal field.

Async response with wait=false

Task status codes

Supported file formats

Authentication

ADP MCP Server uses API key authentication through a URL query parameter:
  • Get the API key from My MCP in the ADP console.
  • Each API key is bound to one user and can access only that user’s applications and data.
  • The API key is used only for authentication and does not appear in request or response bodies.

FAQ

The tool list is generated dynamically based on applications initialized for the current user. On first connection, the system initializes all out-of-the-box applications. Refresh the tool list after initialization.
Make sure the uploaded file matches the tool type. For example, use extract_id_card for ID card images, not extract_vehicle_cert. The file must be a supported image or PDF.
The default timeout is 300 seconds. You can set timeout_seconds up to 900 seconds. For large or complex documents, use wait=false and query the result with task_id.
They provide equivalent capabilities but use different integration methods.

Support

OpenAPI guide

API documentation

Public cloud user guide

ADP user guide

License

  • MCP Server: Free access as part of the ADP product.
  • ADP service: Public cloud AI document processing service billed by usage. New users receive 100 free credits each month.