Skip to content
Activepieces Platform logo

Activepieces Platform MCP server

Open source no-code business automation

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

Tools
4
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the Activepieces Platform MCP server

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

Tools

Activepieces Platform tools your AI can run

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

  • Create Project

    Create a new project

    1 field

  • Update Project

    Update a project

    4 fields

  • List Projects

    List all projects

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Activepieces Platform

Connect Activepieces Platform 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.

Activepieces Platform MCP, answered.

No. That is the point of it. One Activepieces server exposes Activepieces Platform 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 Activepieces Platform 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 4 tools, including Create Project, Update Project, List Projects, 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.