Skip to content
Approval (Legacy) logo

Approval (Legacy) MCP server

Build approval process in your workflows

Approval (Legacy) 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
License
MIT, open source
Updated
August 2026

About the Approval (Legacy) MCP server

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

Tools

Approval (Legacy) tools your AI can run

Once connected, your assistant can call any of these Approval (Legacy) actions by asking in plain language.

  • Wait for Approval

    Pauses the flow and wait for the approval from the user

    1 field

  • Create Approval Links

    Create links only without pausing the flow, use wait for approval to pause

    1 field

Approval (Legacy) MCP, answered.

No. That is the point of it. One Activepieces server exposes Approval (Legacy) 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 Approval (Legacy) 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 Wait for Approval, Create Approval Links, 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.