# Activepieces (MCP archived)

> Open-source workflow automation — trigger and manage from an AI agent. Community MCP wrapper archived; Activepieces itself is unaffected.

[Canonical HTML page](https://top-mcps.com/mcp/activepieces) · [server.json](https://top-mcps.com/mcp/activepieces.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "activepieces": {
      "command": "npx",
      "args": [
        "-y",
        "activepieces-mcp"
      ],
      "env": {
        "ACTIVEPIECES_API_URL": "${ACTIVEPIECES_API_URL}",
        "ACTIVEPIECES_API_KEY": "${ACTIVEPIECES_API_KEY}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export ACTIVEPIECES_API_URL=https://cloud.activepieces.com/api/v1
# export ACTIVEPIECES_API_KEY=your-api-key
claude mcp add activepieces -- npx -y activepieces-mcp
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "activepieces": {
      "command": "npx",
      "args": [
        "-y",
        "activepieces-mcp"
      ],
      "env": {
        "ACTIVEPIECES_API_URL": "${ACTIVEPIECES_API_URL}",
        "ACTIVEPIECES_API_KEY": "${ACTIVEPIECES_API_KEY}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "activepieces": {
      "command": "npx",
      "args": [
        "-y",
        "activepieces-mcp"
      ],
      "env": {
        "ACTIVEPIECES_API_URL": "${ACTIVEPIECES_API_URL}",
        "ACTIVEPIECES_API_KEY": "${ACTIVEPIECES_API_KEY}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "activepieces": {
      "command": "npx",
      "args": [
        "-y",
        "activepieces-mcp"
      ],
      "env": {
        "ACTIVEPIECES_API_URL": "${ACTIVEPIECES_API_URL}",
        "ACTIVEPIECES_API_KEY": "${ACTIVEPIECES_API_KEY}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "activepieces": {
      "command": "npx",
      "args": [
        "-y",
        "activepieces-mcp"
      ],
      "env": {
        "ACTIVEPIECES_API_URL": "${ACTIVEPIECES_API_URL}",
        "ACTIVEPIECES_API_KEY": "${ACTIVEPIECES_API_KEY}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "activepieces-mcp"
          ],
          "env": {
            "ACTIVEPIECES_API_URL": "${ACTIVEPIECES_API_URL}",
            "ACTIVEPIECES_API_KEY": "${ACTIVEPIECES_API_KEY}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.activepieces]
command = "npx"
args = [
  "-y",
  "activepieces-mcp",
]
env = { ACTIVEPIECES_API_URL = "${ACTIVEPIECES_API_URL}", ACTIVEPIECES_API_KEY = "${ACTIVEPIECES_API_KEY}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "activepieces": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "activepieces-mcp"
        ]
      },
      "env": {
        "ACTIVEPIECES_API_URL": "${ACTIVEPIECES_API_URL}",
        "ACTIVEPIECES_API_KEY": "${ACTIVEPIECES_API_KEY}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

Activepieces (MCP archived) doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

```none

```

## At a glance

- **Maintainer:** Community
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** ACTIVEPIECES_API_URL, ACTIVEPIECES_API_KEY
- **Supported clients:** Claude, Cursor, VS Code, Any MCP-compatible client, Activepieces 0.20+
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-31
- **GitHub stars:** 22,436 (fetched 2026-06-02T11:55:52.380Z)
- **Score:** 86/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/activepieces/activepieces

## Security & scope

- **Access scope:** network
- **Sandbox:** Activepieces API key in env. Inherits the issuing user's permissions; scope by user.
- **Gotchas:**
  - Trigger calls execute under the issuing user's connections — the agent inherits whatever credentials those flows use.
  - Cloud and self-hosted have different URLs; mixing them is a common setup error.
  - Long-lived API keys; rotate on the standard cadence.

## Quick answer

**What it does.** Connects to an Activepieces deployment and exposes flow enumeration, on-demand triggering, and run inspection to AI models.

**Best for:**
- Triggering existing Activepieces flows
- Run inspection
- Self-hosted automation workflows
- AI-native flow integration

**Not for:**
- Flow authoring (use the Activepieces UI)
- Teams not already on Activepieces

## Description

A community-maintained MCP for Activepieces, the open-source Zapier alternative. Trigger flows on demand, list available flows, and inspect run history from an AI agent. The full Activepieces feature set — 200+ integrations, AI-native pieces, self-host or cloud — sits behind a small MCP surface. Note: the community activepieces-mcp wrapper is archived — no upstream maintenance. Activepieces itself is current and exposes its own MCP endpoint per flow; new installs should use that.

## Why it matters

Activepieces is the fastest-growing open-source automation platform. An MCP turns the visual flow builder into an agent-callable tool surface.

## Key features

- Self-hosted + cloud support
- API-key auth
- Flow enumeration + trigger
- Run-history inspection
- AI-native pieces visible to the agent

## FAQ

### Self-hosted or cloud?

Both. Pass the API URL of whichever you run. The MCP is identical against either.

### How is auth scoped?

API keys inherit the user identity. For agent use, create a dedicated low-privilege user with access only to the flows the agent should trigger.

### AI-native pieces?

Yes — Activepieces ships pieces designed for LLM-driven steps. The agent sees them in the flow list the same as any other piece.

### Activepieces vs n8n?

Both open-source. Activepieces is younger, has a cleaner React UI, and ships with more AI-first pieces; n8n has the larger ecosystem and longer track record. Pick by what your team already runs.

## Changelog

- **2026-05-31** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-05-08** — Initial directory listing.