Since we launched our core document parsing API, we've had fantastic feedback from developers who love the precision and the "pay-on-accept" model. But as we watched people build more complex systems, we noticed a common pattern: everyone was writing the same boilerplate code to manage their workflows.
Developers were building their own logic to handle workspaces, manage batches of files within tasks, poll for results, and handle state. Our raw API is powerful for single transactions, but it left the orchestration part up to you.
To solve this, we've built and are now launching our MCP (Multi-Channel Platform) server.
Think of it as a stateful, command-based orchestration layer that sits on top of our core parsing API. Instead of you having to write code to manage IDs and track the status of multi-file jobs, the MCP server handles it for you through a simple, logical interface.
The workflow is structured around a clear hierarchy: Workspace -> Task -> File.
You can use straightforward commands like:
- UnDatasIO_get_workspaces to get your work_id.
- UnDatasIO_upload to add files to a specific task_id.
- UnDatasIO_parse to kick off parsing for a list of file_ids.
- UnDatasIO_get_parse_result to poll for the job status without building your own loop.
This is perfect for anyone building complex, multi-file data processing pipelines, integrating with low-code platforms, or who simply wants to manage large batch jobs without the hassle of writing and maintaining state-management code. Our goal is to let you focus on what to do with the data, not the plumbing required to get it.
We believe this will make building robust document workflows much faster and more reliable. We're just getting started and are eager for your feedback.
We've put together a comprehensive guide and a video tutorial to walk you through it.
Since we launched our core document parsing API, we've had fantastic feedback from developers who love the precision and the "pay-on-accept" model. But as we watched people build more complex systems, we noticed a common pattern: everyone was writing the same boilerplate code to manage their workflows.
Developers were building their own logic to handle workspaces, manage batches of files within tasks, poll for results, and handle state. Our raw API is powerful for single transactions, but it left the orchestration part up to you.
To solve this, we've built and are now launching our MCP (Multi-Channel Platform) server.
Think of it as a stateful, command-based orchestration layer that sits on top of our core parsing API. Instead of you having to write code to manage IDs and track the status of multi-file jobs, the MCP server handles it for you through a simple, logical interface.
The workflow is structured around a clear hierarchy: Workspace -> Task -> File.
You can use straightforward commands like: - UnDatasIO_get_workspaces to get your work_id. - UnDatasIO_upload to add files to a specific task_id. - UnDatasIO_parse to kick off parsing for a list of file_ids. - UnDatasIO_get_parse_result to poll for the job status without building your own loop.
This is perfect for anyone building complex, multi-file data processing pipelines, integrating with low-code platforms, or who simply wants to manage large batch jobs without the hassle of writing and maintaining state-management code. Our goal is to let you focus on what to do with the data, not the plumbing required to get it.
We believe this will make building robust document workflows much faster and more reliable. We're just getting started and are eager for your feedback. We've put together a comprehensive guide and a video tutorial to walk you through it.
MCP User Guide (Full API Reference): https://docs.undatas.io/mcp/undatas-mcp/
Video Tutorial on YouTube: https://www.youtube.com/watch?v=_xobbKiPyf4
Our Official Website: https://undatas.io/
I'll be here all day to answer any questions. Let us know what you think