Activepieces

Activepieces is an open-source automation platform positioned as a replacement for Zapier, built around a type-safe, TypeScript "pieces" framework. Every piece is an open-source npm package, and roughly 60% of the 280+ available pieces are community-contributed. Pieces double as MCP servers, so the same integrations can be used directly by LLM clients like Claude Desktop, Cursor, or Windsurf.

Key features

• 280+ pieces: prebuilt integrations for Google Sheets, OpenAI, Discord, RSS, and hundreds of other services.
• MCP server support: every piece is exposed as an MCP tool usable from Claude Desktop, Cursor, or Windsurf.
• Builder primitives: loops, branches, auto-retries, HTTP requests, and code steps with NPM package access.
• AI-first pieces: native pieces for multiple AI providers, plus an AI SDK for building custom agents inside flows.
• Human-in-the-loop: delay execution or require manual approval before a flow continues.
• Human input interfaces: built-in chat and form interfaces for triggering or interacting with flows.
• Self-hosted and network-gapped: designed to run fully on your own infrastructure for data control.

Ideal use cases

Activepieces fits teams replacing a paid workflow-automation SaaS with something they can run on their own infrastructure, particularly organizations with data residency requirements that rule out sending business data through a third-party automation vendor's servers. The MCP server angle broadens that further: because every piece is already exposed as an MCP tool, teams building internal AI assistants or agents can reuse the same 280+ integrations Activepieces ships, without writing separate tool definitions for each service. Human-in-the-loop steps make it suitable for workflows that need a manual approval gate, such as finance approvals or content review, rather than purely unattended automation. Because pieces are versioned npm packages developed with hot reloading, teams with in-house or niche SaaS tools can build and maintain a private piece without waiting on the open-source project to add support, then keep it inside their own deployment rather than publishing it publicly. The chat and form interfaces built into flows also let non-technical teams trigger automations directly, without wiring up a separate frontend. Flows are versioned, so a change to a live automation can be reviewed and rolled back the same way a code change would be, which matters for teams running business-critical automations rather than one-off scripts.

Self-hosting and deployment

Activepieces Community Edition is MIT-licensed and self-hostable, with enterprise features gated behind a separate commercial license covering the packages under packages/ee. Deployment instructions live in the project's install docs, and new pieces can be developed locally with hot reloading before being published to npm as versioned packages. Because pieces are just TypeScript npm packages, teams can build private integrations following the same contributor guide used for the 200+ community pieces already shipped.