Head to head · Workflow automation · October 2026 research run

Activepieces API + MCP vs Make API + MCP

Make API + MCP scores 64.6 (B) on agent readiness against Activepieces API + MCP's 59.3 (C), and leads in 2 of 7 scored categories. Activepieces API + MCP leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community. Both do workflow automation.

Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons

Which one, for what

Activepieces API + MCP C

Best for A team that wants an MIT-licensed builder it can self-host or embed, with an agent that builds flows through MCP.

Ahead on

  • Schema & documentation, 83 against 66
  • Agent ergonomics, 70 against 63
  • Payments & pricing, 60 against 45
  • Maintenance & community, 80 against 56

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

Docs say API keys come from the platform dashboard in Platform and Enterprise editions, while the pricing page lists API access on every plan

Make API + MCP B

Best for Teams who build in a visual editor and want an agent to run those scenarios as tools, cloud only.

Ahead on

  • Reliability, 73 against 65

Also in its favour

  • No incidents deducted, where Activepieces API + MCP loses 11 points for them

Watch for

No published OpenAPI file and no official SDK for the REST API

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Activepieces API + MCP +24

Activepieces API + MCP 80

0.92.3 tagged on 12 October 2026, with hotfix tags 0.92.3-hotfix.1 (23 October) and -hotfix.2 (28 October) (30). 18 stable tags from 0.88.0 (12 August) to 0.92.3 in the 90 days from 6 August (20). Per the 1 October check, not re-read on 4 November, 381 open issues labelled by area and priority, reply times unread (15). An embed SDK on npm, but no official REST SDK and no entry in the official MCP registry found, so the line is partly met and keeps its earlier 5 of 15 pending a rule on in-between values. CI runs typecheck, build, unit, API and end-to-end tests, plus DAST and a breaking-change check (10). 30 + 20 + 15 + 5 + 10 = 80.

Make API + MCP 56

Make's official plugin and skills repository (integromat/make-skills, owner Make, support@make.com) is a dated vendor source. Plugin version 0.2.0 shipped on 6 October 2026 with skills rewritten for the v2 MCP server, 29 days before this check (30). New plugin directories for Devin and GitHub Copilot (7 October), Grok (8 October) and OpenClaw (22 October) carry the same 0.2.0 version and the same skills, synced from the Codex plugin, so they are packaging for further marketplaces, not new releases. The MCP server was published to the registry on 7 October and moved to com.make/mcp-server 2.0.0 on 30 October, a listing change recorded but not counted. The repository has no tags, its CHANGELOG stops at 0.1.7 (29 May), and the white-label release notes still stop at 2026.05, undated. One dated release in the 90 days to 4 November (0). Public release notes with dated deprecations and a community forum. We didn't test a support channel (8). Listed in the official MCP registry as com.make/mcp-server, per the repository's server.json (15). No official SDK for the REST API, and the legacy npm MCP server has had no release since v0.5.0 (3). 30+0+8+15+3 = 56.

Schema & documentation Activepieces API + MCP +17

Activepieces API + MCP 83

OpenAPI 3.1 file at docs/openapi.json with 84 paths and 119 operations, and zod input schemas on every MCP tool (25). llms.txt at /docs/llms.txt lists 318 Markdown pages (10). Tool descriptions state purpose and consequences, for example ap_delete_flow says it can't be undone, but rarely when not to call (14). Typed inputs with IDs and enums, few free-form blobs (12). The OpenAPI file lists only 200, 201 and 204 responses, no error bodies, though the docs have request examples (7). Semver release tags, a public changelog with month-labelled entries and a breaking-changes page per release, though the spec's version is 0.0.0 (15, was 12, not a checklist value). 25 + 10 + 14 + 12 + 7 + 15 = 83.

Make API + MCP 66

No OpenAPI file. MCP tools get typed inputs from each scenario's input definitions, so half credit (10). llms.txt with about 380 entries and a Markdown copy of every page (10). API reference pages state each endpoint's purpose. MCP tool descriptions come from whatever the scenario owner wrote (10). Typed, documented parameters on the API, and scenario inputs typed by their owner (10). A single error schema with detail, message and code, Make-specific codes (IM001 to IM102, SC403) and request examples (13). Versioned at /api/v2, with white-label release notes and dated deprecation notices (13). Re-read on 4 November, llms.txt has 541 lines, and its pages carry a GitBook "Agent Instructions" block, treated as data. 10+10+10+10+13+13 = 66.

Payments & pricing Activepieces API + MCP +15

Activepieces API + MCP 60

No x402, MPP or L402 (0). Plan prices and $0.007 per extra credit are public, and the pricing page now says what a credit buys (a run is one credit however many steps, AI steps 2, 10 or 20 credits by model tier, agentic actions 1) (20, was 15). Free plan of 1,000 credits a month, no card and no time limit (20). A person signs up in the browser or installs an instance (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Make API + MCP 45

No x402, MPP or L402 (0). Plan prices are public and priced in credits, one per module action, but we found no published per-credit price for extra bundles (10). Free plan of 1,000 credits a month with no card (20). A person signs up in the browser and creates a token per zone (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Reliability Make API + MCP +8

Activepieces API + MCP 65

Better Stack status page at status.activepieces.com with two components, API Health and Worker Health (20). Its feed shows no incident in the 90 days from 6 August 2026; the 26 July Worker Health incident has left the window, so a clean record (30). No request-rate limit for the API was found. The limits page gives run, memory, concurrency (5 to 30 concurrent runs per project by plan), webhook and storage limits with numbers, which aren't request rate limits, so the line is partly met and keeps its earlier 5 of 15 pending a rule on in-between values. No 429 or backoff guidance found (0). The terms set a 48-hour first-response support SLA on Business and Platform plans and no availability SLA (0). API and MCP server are generally available (10). 20 + 30 + 5 + 0 + 0 + 10 = 65.

Make API + MCP 73

Statuspage at status.make.com with incidents per zone (20). history.atom, re-read on 4 November, lists ten incidents from 6 August, each one zone, one app or a subset of scenarios. They are AI models on eu1 and us2 (10 August), a subset of scenarios disabled after a release and re-enabled after a rollback (14 August), saving and manual runs on EU2 (24 August), delays on EU1 for 20 minutes (26 August) and US2 for 45 minutes (2 September), degradation on eu1.make.com (9 and 10 September) and us1.make.celonis.com (18 September), UI logs with the API unaffected (23 September), scenarios using the Scenario app (12 October) and shared-webhook events not processed for 27 minutes (2 November). All partial, so minor only (20). The 1 October note read no August or September entries; the feed lists them now. API limits published per organisation, 60 calls a minute on Core, 120 on Pro, 240 on Teams and 1,000 on Enterprise (15). The 429 answer says "please try again later", with no Retry-After header, backoff or safe-retry advice for writes (8). Celonis's legal page for Make lists a "Support Service Description and Service Level Agreement for Make" for Enterprise, on a document host whose robots.txt disallows every path, so its terms are unread. An SLA whose terms we couldn't read isn't credited, as serpkite, socure-riskos, affinity and cloudflare-workers-ai were read (0). The API and the hosted MCP server aren't marked beta (10). 20+20+15+8+0+10 = 73.

Agent ergonomics Activepieces API + MCP +7

Activepieces API + MCP 70

47 MCP tools in groups, so 5, plus 10 back because groups can be switched off per project and ap_search_actions finds actions by task description instead of listing pieces (15). Every endpoint uses seek pagination with limit and cursor, and list endpoints take filters (20, was 18). API errors aren't documented in the spec or the API pages, while the MCP tools return actionable error text, such as a not-found message that names the tool to call next, so the line is partly met (8 of 20). All 47 registered tools set both readOnlyHint and destructiveHint, 17 of them with destructiveHint: true, and 42 set idempotentHint (20, was 17). Few required parameters, but the only official client is the JavaScript embed SDK, not SDKs in two languages, so partly met (7 of 15). The two partly met lines keep their earlier values pending a rule on in-between values. 15 + 20 + 8 + 20 + 7 = 70.

Make API + MCP 63

Tools are one per on-demand scenario plus management tools on paid plans, and a token's access control limits which scenarios appear. We couldn't count the management tools (15). Documented pagination, sorting and filtering on list endpoints (20). Errors carry codes an agent can branch on, such as IM002 for insufficient rights and 429 for the rate limit (18). We found no tool annotations or idempotency keys (5). No official SDK, and the base URL changes per zone, six of them now (5). Make's own skills name more than 40 MCP tools (scenario_get, scenario_patch, function_run_create and others), but no count is published and none was taken from a live server, and scopes decide which tools a key sees. 15+20+18+5+5 = 63.

Score by category

CategoryWeightActivepieces API + MCPMake API + MCPEdge
Reliability16%6573Make API + MCP +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8366Activepieces API + MCP +17
Agent ergonomics13%7063Activepieces API + MCP +7
Security & auth14%6468Make API + MCP +4
Payments & pricing10%6045Activepieces API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8056Activepieces API + MCP +24
Transparency & trust7%7775Activepieces API + MCP +2
Negative events≤15-110
TotalC 59.3/100B 64.6/100

Facts side by side

FactActivepieces API + MCPMake API + MCP
KindHTTP APIHTTP API
VendorActivepiecesMake (Celonis)
Hosted endpointhttps://cloud.activepieces.com/api/v1https://eu1.make.com/api/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (core), commercial licence for enterprise-only partsproprietary
Tools exposed47none
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.make/mcp-server
Last release2026-10-122026-10-06
Terms last updatedcouldn't be readcouldn't be read
Privacy policy last updatedcouldn't be readcouldn't be read
Customer content may train modelscouldn't be readcouldn't be read
Terms restrict automated accesscouldn't be readcouldn't be read
Terms restrict benchmarkingcouldn't be readcouldn't be read
Terms or service can change without noticecouldn't be readcouldn't be read
Arbitration or class-action waivercouldn't be readcouldn't be read
Popularity25k stars, 452k npm/wknone
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Activepieces API + MCP higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Activepieces API + MCP

MIT core, self-hostable, with an MCP server whose 47 tools all carry read-only or destructive annotations and a free Cloud plan with no card. The OpenAPI file documents no errors and no request rate limits are published, and eight advisories from July and August 2026 were followed by October piece fixes for SSRF and a password leak with no advisory.

Make API + MCP

Hosted MCP server with OAuth and scenario run tools on the free plan, and API limits published per plan. Incidents since August each hit one zone or a subset of scenarios. No published OpenAPI file, no official SDK for the REST API, and the MCP key can travel in the URL path.

Before you call either

Activepieces API + MCP

  1. Run ap_validate_flow before publishing a flow
  2. Use ap_search_actions with a plain task description rather than listing pieces
  3. Turn off the Flow Building and Tables groups for a project the agent should only read
  4. Page with limit and cursor and stop when next is null
  5. Cloud runs stop at 10 minutes of active time. Waits and approvals don't count

Make API + MCP

  1. Find the organisation's zone first. It may be on make.com or make.celonis.com
  2. Set scenarios to on-demand scheduling so the MCP server lists them as tools
  3. Use the header form at /mcp/v2 rather than the /mcp/u/<key>/v2 path form
  4. On a 429, wait a full minute before retrying. The limit is per minute and no Retry-After is sent
  5. If a scenario tool call times out, keep the returned executionId and fetch the result later; scenarios run for up to 40 minutes

Questions

Which is better for AI agents, Activepieces API + MCP or Make API + MCP?

Make API + MCP scores 64.6 (B) on agent readiness against Activepieces API + MCP's 59.3 (C), and leads in 2 of 7 scored categories. Activepieces API + MCP leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community.

Do Activepieces API + MCP and Make API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Activepieces API + MCP and Make API + MCP without installing anything?

Yes. Activepieces API + MCP has a hosted endpoint at https://cloud.activepieces.com/api/v1 and Make API + MCP at https://eu1.make.com/api/v2.

Are Activepieces API + MCP and Make API + MCP open source?

Activepieces API + MCP is open source (MIT (core), commercial licence for enterprise-only parts). No open-source release is listed for Make API + MCP.

Other comparisons with Activepieces API + MCP or Make API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.