Yes. Activepieces' Community Edition is MIT licensed and self-hostable for free, and all MCP tools are open source. Enterprise-only features carry a commercial license, and the hosted cloud has its own plans.

Does it support remote/OAuth?

It is a remote MCP server exposed as a per-project SSE endpoint. Authorization is carried by a unique token embedded in the server URL you generate in the dashboard; each piece additionally uses the connection you authenticated inside Activepieces.

Activepieces MCP server

OfficialActivepieces22,504Config last verified Jun 1, 2026

Activepieces' official MCP server turns its open-source automation pieces and flows into agent tools through a per-project remote endpoint.

Activepieces is an open-source, self-hostable automation platform (an MIT-licensed alternative to Zapier and n8n) with a visual flow builder on top of a strongly typed integration SDK. Its official MCP server is what makes that whole catalog usable by an AI agent: rather than shipping a fixed handful of tools, it exposes the pieces and flows you connect inside Activepieces as callable MCP tools. With 280-plus pieces (and growing) covering hundreds of SaaS apps, the agent reaches your real stack, Slack, GitHub, Google, databases, and more, through one endpoint, and each tool inherits the authenticated connection you configured in Activepieces.

Because the tool surface is dynamic, you curate it: in the Activepieces dashboard under AI then MCP you connect the specific pieces and flows you want to expose, and you get a unique per-project server URL. That URL is an SSE endpoint of the form https://cloud.activepieces.com/api/v1/mcp/<token>/sse, where the embedded token both identifies the project and authorizes access; self-hosted instances expose the same path on your own domain. You point an MCP client such as Claude Desktop, Cursor, or Windsurf at that URL and the agent immediately sees the tools you enabled. The exact tool names therefore depend on which pieces and flows you connect rather than a fixed built-in list.

Quick install

Copy-paste configs are provided for all 8 supported clients. Pick your client below.

Add to ~/.claude.json

~/.claude.json

json

{
  "mcpServers": {
    "activepieces": {
      "type": "http",
      "url": "https://cloud.activepieces.com/api/v1/mcp/YOUR_TOKEN/sse"
    }
  }
}

Or via CLI

bash

claude mcp add --transport http activepieces https://cloud.activepieces.com/api/v1/mcp/YOUR_TOKEN/sse

Step-by-step guides

What you can do with it

Give an agent reach across your SaaS stack

Connect the pieces you trust (Slack, GitHub, Google Sheets, a database) in the Activepieces dashboard, then point an MCP client at your per-project URL so the agent can act across all of them through one endpoint.

Expose a curated automation as a tool

Build a multi-step flow in Activepieces and expose it over MCP so an agent can trigger that whole automation as a single callable tool, keeping complex orchestration on the platform.

FAQ

Is it free?: Yes. Activepieces' Community Edition is MIT licensed and self-hostable for free, and all MCP tools are open source. Enterprise-only features carry a commercial license, and the hosted cloud has its own plans.
Does it support remote/OAuth?: It is a remote MCP server exposed as a per-project SSE endpoint. Authorization is carried by a unique token embedded in the server URL you generate in the dashboard; each piece additionally uses the connection you authenticated inside Activepieces.
What tools does it expose?: Whichever pieces and flows you connect. The tool list is dynamic: you curate it in the Activepieces dashboard under AI then MCP, so there is no fixed built-in tool set, drawing from 280-plus available pieces.

← Browse all automation servers