# Activepieces [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/activepieces/activepieces  
**GitHub Stars:** 25155  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/activepieces

## Description
Open-source workflow automation platform (Zapier alternative) whose integration pieces are exposed as MCP servers for AI agents.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Activepieces MCP server does

Activepieces MCP server connects AI agents with Activepieces pieces: open-source integration packages that expose service-specific capabilities through MCP. The repository describes more than 200 pieces, including integrations for Google Sheets, OpenAI, Discord, and RSS. Each piece is distributed as a TypeScript package and can become available to MCP-compatible clients.

This makes the project relevant when an agent needs to work with services already supported by Activepieces, or when a team wants to add an integration rather than maintain a separate agent-specific connector. The available operations depend on the selected piece; the provided material does not list a fixed set of MCP tool names.

Activepieces is also a workflow automation platform. Its builder supports loops, branches, automatic retries, HTTP steps, code using npm packages, versioned flows, translations, and customizable templates. These builder functions are platform capabilities and should not be assumed to be individual MCP tools unless exposed by a particular piece.

## How it works

Integrations are implemented as “pieces” using Activepieces’ type-safe TypeScript framework. When a piece is contributed, it becomes available as an MCP server for use with language models. Pieces are versioned and published to npm, and their source code is available in the repository. The project also supports hot reloading for local piece development.

The ecosystem includes both project-maintained and community-contributed pieces; the README states that 60% of the pieces come from the community. Developers can create their own piece with the framework, then use it within Activepieces and expose it to MCP clients. This approach means the server’s practical coverage changes with the installed or available pieces rather than being limited to one fixed external API.

## Tools and capabilities

The Activepieces MCP server provides access to capabilities supplied by Activepieces pieces. Supported examples named by the project include:

- Google Sheets integration
- OpenAI integration
- Discord integration
- RSS integration
- More than 200 additional pieces
- Custom pieces written in TypeScript

The broader Activepieces platform adds workflow features such as loops, branches, retries, HTTP requests, npm-backed code steps, and flow versioning. It also includes native AI pieces, human approval or delay steps, and human-input interfaces such as chat and forms. Whether these features are available directly to an agent depends on how the relevant piece exposes them.

## Limitations and notes

The README does not provide a universal tool schema, command example, environment-variable list, or per-piece authentication instructions. Configuration therefore depends on the chosen Activepieces deployment and integration, and developers should consult the project documentation for installation and piece-specific setup.

Activepieces MCP server is described as usable with Claude Desktop, Cursor, and Windsurf. The project supports self-hosted and network-gapped deployments, which may suit environments that need to keep automation data under local control. The Community Edition uses the MIT license, while enterprise features use a separate commercial license. Integration availability and behavior may change as pieces are contributed and updated.

_Full upstream README: https://allmcps.com/mcp/activepieces/readme_