Skip to content
FlowParser logo

FlowParser MCP server

Upload, process, and manage documents programmatically with FlowParser's REST API.

FlowParser is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
1
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
August 2026

About the FlowParser MCP server

Connect FlowParser once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches FlowParser and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

FlowParser tools your AI can run

Once connected, your assistant can call any of these FlowParser actions by asking in plain language.

  • Upload Document

    Upload a new document to FlowParser for processing

    1 field

Triggers

FlowParser events your agent can watch

These start a run the moment something happens in FlowParser, so work gets picked up on its own.

  • New Parsed Document by Template

    Triggers when a new document is parsed using a specific template

    1 field

  • New Parsed Document Found

    Triggers when a document has been successfully parsed

Give your assistant FlowParser

Connect FlowParser once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

FlowParser MCP, answered.

No. That is the point of it. One Activepieces server exposes FlowParser alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect FlowParser in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 1 tool, including Upload Document, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.