Head to head · Workflow automation · October 2026 research run

Activepieces API + MCP vs n8n API + MCP

Activepieces API + MCP scores 59.3 (C) on agent readiness against n8n API + MCP's 49.3 (D), and leads in 2 of 7 scored categories. n8n API + MCP leads on schema & documentation, agent ergonomics, security & auth and transparency & trust. 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

  • Reliability, 65 against 20
  • Payments & pricing, 60 against 45

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • 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

n8n API + MCP D

Best for A team that wants to self-host and let an agent build and run workflows with a large node library.

Ahead on

  • Schema & documentation, 92 against 83
  • Agent ergonomics, 79 against 70
  • Security & auth, 70 against 64
  • Transparency & trust, 87 against 77

Watch for

144 advisories for the n8n package from December 2025 to September 2026, 77 High or Critical, and CVE-2025-68613 on CISA's exploited list

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.

Reliability Activepieces API + MCP +45

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.

n8n API + MCP 20

Status page at status.n8n.cloud is an UptimeRobot page. On 4 November its HTML showed only "Loading..." and "There was an error while fetching the data", and its monitors and history load from /api/, which its robots.txt closes. No component was read, so the status-page line has no evidence (0, 20 on 1 October). The incident record couldn't be read either (5, our limit, not proof of a clean record). No request rate limit for the public API is documented. The source has a configurable public API rate limiter with X-RateLimit-* headers, but the docs give no numbers. Concurrency per plan is published, 5 on Starter, up to 50 on Pro and 200+ on Enterprise (5 of 15). No 429, Retry-After or backoff guidance was found. Since 2.45.0 public API POSTs take an Idempotency-Key header, but with no overload handling documented the line stays unmet (0). Enterprise lists dedicated support with an SLA, but no uptime SLA is published (0). The REST API and the instance MCP server are generally available (10). Total 0+5+5+0+0+10 = 20.

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.

n8n API + MCP 45

No x402, MPP or L402 (0). Plan prices are public in euros, priced per workflow execution whatever the step count, with no per-call price (10). Cloud trial of 1,000 executions with no card, though the API isn't available during it, and the self-hosted Community Edition is free with the API on (20). A person has to sign up or install an instance and create a key in the UI (0). Total 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Transparency & trust n8n API + MCP +10

Activepieces API + MCP 77

The editorial half. MIT core with enterprise folders under a commercial licence, both stated in LICENSE and the docs (27). Cloud run data kept 30 days per the limits page. The privacy policy (19 January 2026) now renders without a browser and says data is kept while an account is active, names Google Analytics and Stripe, and says it doesn't sell data. No DPA or sub-processor list is published (on request per the pricing page) (12). A breaking-changes page per release with what to do, and a month-labelled changelog (15). Self-hosted product analytics on by default, documented with an opt-out and the claim that no personal information is collected, which the code bears out for self-hosted editions (email and names go to PostHog only on Cloud). Licensed instances also send a daily deployment snapshot, on by default with its own switch. Cloud data sits in Frankfurt by default (16). 27 + 12 + 15 + 16 = 70.

n8n API + MCP 87

Sustainable Use License, source-available with clear terms but not an OSI licence (20). Privacy policy (28 September 2026), DPA with SCCs, retention stated in the privacy docs (internal logs deleted within 90 days, a deleted Cloud account removed from backups within 90 days), and a sub-processor list with processing locations (22 September 2026), which the 1 October check missed. Execution log retention is stated per plan (28, 22 on 1 October). BREAKING-CHANGES.md and a 3.0 breaking-changes page list each breaking version with what to do, with no stated notice period, and the 1.x line still gets patches alongside 2.x (15). Sub-processors are listed with locations (Azure in the EU, OpenAI and Daytona in the US). Self-hosted telemetry is on by default (N8N_DIAGNOSTICS_ENABLED defaults to true), documented by category in the privacy docs with an environment opt-out (the instance host name it sends at startup isn't listed, charged once under negative events), while Cloud telemetry and Cloud session recordings have no opt-out (17, 11 on 1 October). Total 20+28+15+17 = 80.

Schema & documentation n8n API + MCP +9

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.

n8n API + MCP 92

OpenAPI 3.0 file for the public API in the repository (version 1.1.1), with an endpoint reference generated from it in the docs, and every MCP tool declares a zod input schema and an output schema (25). llms.txt at docs.n8n.io and a Markdown copy of every docs page (10). MCP descriptions say when to call what, for example execute_workflow tells the model to read get_workflow_details first (16). Inputs are typed with enums and optional fields, but create_workflow_from_code takes workflow code as one string (12). Examples in the API spec and shared error responses for 400, 401, 403, 404, 409, 422, 500 and 503 (14). Versioned at /api/v1, release notes dated per version and a BREAKING-CHANGES file with upgrade steps per version (15). Total 92.

Agent ergonomics n8n API + MCP +9

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.

n8n API + MCP 79

57 MCP tools in the tools reference on 4 November (54 on 1 October), so 5, plus 10 back because OAuth scopes such as workflow:read and execution:read only register the tools they cover, and builder tools sit behind a flag (15). Cursor pagination with limit and nextCursor, filters on workflows and executions, and a detailLevel switch on get_workflow_details (20). Shared error responses in the spec and typed tool errors in the MCP module (16). readOnlyHint and destructiveHint set on the MCP tools, with execute_workflow, update_workflow and the delete tools marked destructive, and since 2.45.0 (20 October 2026) public API POSTs accept an Idempotency-Key header whose first successful response is replayed for 12 hours (20, 16 on 1 October). Few required parameters, but no official REST SDK in any language (8). Total 79.

Security & auth n8n API + MCP +6

Activepieces API + MCP 64

REST API keys as bearer tokens per platform, with no scopes found. The MCP server signs in with OAuth and PKCE, is bound to one project, and grants sit on a revocation list. It has one mcp scope (22). Tool groups can be turned off per project, each tool checks the user's project permission, and nothing asks for confirmation before a destructive tool (13). Tools never return connection secrets and ap_setup_guide sends the user to the UI, but run output from third-party apps comes back with no injection guidance (6). Enterprise audit log with event streaming records agent writes. The docs say MCP tool calls aren't recorded in it, only in an activity feed (10). SECURITY.md, private GitHub reporting, published advisories and a private, invite-only bug bounty. No security.txt; the pricing page says the SOC 2 programme is in progress and a penetration test summary, DPA and sub-processor list are sent on request (13).

n8n API + MCP 70

REST keys go in X-N8N-API-KEY, carry an expiry and can be deleted, but scopes are Enterprise only. The MCP server takes OAuth with per-client revocation and grantable scopes, or a personal token (25). Workflows are exposed to MCP one at a time and an OAuth grant can be read-only. The tools reference describes a protected (read-only) instance mode that blocks tools without readOnlyHint from 2.47.0, which was a beta on 4 November (the stable tag was 2.46.6), and nothing asks for confirmation before a destructive tool runs (14). Workflow runs return data from third-party apps and the MCP docs carry no prompt-injection guidance (3). Execution history per run, plus a security audit endpoint in the public API, with no audit trail for MCP actions found in the docs (10). security.txt expiring 31 December 2027 with a disclosure policy, SECURITY.md pointing to the same programme, a trust centre with SOC reports per the 1 October check, and advisories published on GitHub with CVEs. No bug bounty found (18). Total 70.

Score by category

CategoryWeightActivepieces API + MCPn8n API + MCPEdge
Reliability16%6520Activepieces API + MCP +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8392n8n API + MCP +9
Agent ergonomics13%7079n8n API + MCP +9
Security & auth14%6470n8n API + MCP +6
Payments & pricing10%6045Activepieces API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8080even
Transparency & trust7%7787n8n API + MCP +10
Negative events≤15-11-15
TotalC 59.3/100D 49.3/100

Facts side by side

FactActivepieces API + MCPn8n API + MCP
KindHTTP APIHTTP API
VendorActivepiecesn8n
Hosted endpointhttps://cloud.activepieces.com/api/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (core), commercial licence for enterprise-only partsSustainable Use License (fair-code, source-available)
Tools exposed4757
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-122026-11-04
Terms last updatedcouldn't be readcouldn't be read
Privacy policy last updatedcouldn't be read2026-09-28
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/wk206k stars, 113k npm/wk
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.

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.

n8n API + MCP

OpenAPI 3.0 spec, Markdown docs with llms.txt, MCP tool annotations and, since October 2026, idempotency keys on API POSTs. 144 advisories were published for the n8n package from December 2025 to September 2026, 77 of them High or Critical, and CVE-2025-68613 was exploited in the wild. The status page's history couldn't be read.

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

n8n API + MCP

  1. Check the instance version before trusting it. Anything older than 2.38.2 or 1.123.76 carries High advisories published on 10 September 2026
  2. Ask for only the OAuth scopes the job needs. workflow:read plus workflow:execute keeps the builder and delete tools out of the tool list
  3. Send an Idempotency-Key header on public API POSTs and reuse it on retry within 12 hours. A 409 means the first request is still running
  4. Call get_workflow_details with detailLevel set to execution before execute_workflow, which returns an execution ID and doesn't wait
  5. On Cloud trial accounts /api/v1 won't answer. Use the MCP server or a paid plan

Questions

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

Activepieces API + MCP scores 59.3 (C) on agent readiness against n8n API + MCP's 49.3 (D), and leads in 2 of 7 scored categories. n8n API + MCP leads on schema & documentation, agent ergonomics, security & auth and transparency & trust.

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

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

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

Activepieces API + MCP has a hosted endpoint at https://cloud.activepieces.com/api/v1. No hosted endpoint is listed for n8n API + MCP.

Are Activepieces API + MCP and n8n 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 n8n API + MCP.

Other comparisons with Activepieces API + MCP or n8n 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.