Skip to content
Airparser logo

Airparser MCP server

Extract structured data from emails, PDFs, or documents with Airparser.

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

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

About the Airparser MCP server

Connect Airparser 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 Airparser and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Airparser tools your AI can run

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

  • Get Data from Document

    Retrieves parsed JSON data from a specific document.

    2 fields

  • Upload Document

    Upload a document to an Airparser inbox for parsing.

    4 fields

Triggers

Airparser events your agent can watch

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

  • Document Parsed

    Triggers when a new document is parsed in a specific inbox.

    2 fields

Give your assistant Airparser

Connect Airparser 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.

Airparser MCP, answered.

No. That is the point of it. One Activepieces server exposes Airparser 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 Airparser 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 2 tools, including Get Data from Document, 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.