Head to head · Workflow automation · October 2026 research run
n8n API + MCP vs Pipedream API + MCP
Pipedream API + MCP scores 72.8 (BB) 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 and transparency & trust. Both do workflow automation.
Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons
Best auth and delegated access for AI agents · All 168 agent auth comparisons
Which one, for what
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 74
- Agent ergonomics, 79 against 73
- Transparency & trust, 87 against 75
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
Best for Best when an agent acts in many third-party apps on behalf of your own users and you don't want to run OAuth yourself.
Ahead on
- Reliability, 82 against 20
- Payments & pricing, 60 against 45
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- No incidents deducted, where n8n API + MCP loses 15 points for them
Watch for
Public product changelog's last entry is 1 October 2025
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 Pipedream API + MCP +62
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.
Pipedream API + MCP 82
Atlassian Statuspage at status.pipedream.com with components for the REST and Connect APIs, event sources, workflows, frontends and integrations (20). history.atom, read on 1 November, has one incident in the 90 days from 3 August, a string.com chat problem on 5 October that the vendor says left 'all pipedream.com services and workflows' unaffected, so none touches the API. The 28 and 29 July HTTP trigger incidents left the window on 27 and 28 October, so the record is clean (30). Connect API limits are published with numbers, 3,500 token requests per 5 minutes per OAuth client, 2,000 account calls and 3,000 component listings per 5 minutes per project and 5,000 combined project-management calls, but none for action runs or tool calls (12). The rate-limits page, re-read on 1 November, documents 429 Too Many Requests with Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset and says to wait for the window and back off exponentially, with no idempotency keys or safe-retry guidance for action runs, which write to third-party apps (10 of 15). The pricing page lists 'SLAs' and priority support on Business with no figure or SLA document (0). Connect API and MCP server are generally available (10).
Schema & documentation n8n API + MCP +18
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.
Pipedream API + MCP 74
OpenAPI file at pipedream_openapi_swagger.json per the 30 September check, and every MCP tool carries a JSON Schema built from the component's props (25). llms.txt per the 30 September check (10). Component descriptions state what the action does and link the upstream API docs, rarely when not to use it (12). Props are typed with options and required flags, though custom request actions take free-form JSON (11). Tool failures come back with isError and an attribution of where the error came from. Interactive API reference with examples (9). The API is under /v1 and the SDKs follow semver, but the public changelog's last entry is 1 October 2025 (7).
Payments & pricing Pipedream API + MCP +15
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.
Pipedream API + MCP 60
No x402, MPP or L402 (0). Per-unit prices are public. One credit is 30 seconds of compute at 256 MB, extra credits cost $0.012, and end users beyond 100 cost $2 each on Startup (20). Free plan with no card, limited to development (20). A person signs up and creates an OAuth client in the browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Transparency & trust n8n API + MCP +12
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.
Pipedream API + MCP 75
Hosted service under clear terms, with component code under the Pipedream Source Available License, which bars competing commercial use (18). The privacy and security docs state AWS us-east-1 hosting, internal logs deleted within 30 days, customer data kept until you delete it, a subprocessor page and a DPA with SCCs in the terms (24). No deprecation policy, and the terms let Pipedream withdraw anything in Early Access without notice (5). Subprocessors and data location published (18).
Agent ergonomics n8n API + MCP +6
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.
Pipedream API + MCP 73
More than 10,000 tools, so 5, plus 10 back because the x-pd-app-slug header narrows the server to one app's tools (15). Cursor pagination on list endpoints through the SDKs, and app search by name (15). Tool errors carry isError and an origin attribution an agent can act on (15). Since 1 October 2025 every action declares readOnlyHint, destructiveHint and openWorldHint, for example Gmail send-email is a non-destructive, open-world write. No idempotency keys for action runs (15). Official SDKs for TypeScript, Python and Java, but the MCP server needs five headers on every request (13).
Score by category
| Category | Weight | n8n API + MCP | Pipedream API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 20 | 82 | Pipedream API + MCP +62 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 74 | n8n API + MCP +18 |
| Agent ergonomics | 13% | 79 | 73 | n8n API + MCP +6 |
| Security & auth | 14% | 70 | 66 | n8n API + MCP +4 |
| Payments & pricing | 10% | 45 | 60 | Pipedream API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 79 | n8n API + MCP +1 |
| Transparency & trust | 7% | 87 | 75 | n8n API + MCP +12 |
| Negative events | ≤15 | -15 | 0 | |
| Total | D 49.3/100 | BB 72.8/100 |
Facts side by side
| Fact | n8n API + MCP | Pipedream API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | n8n | Pipedream (Workday) |
| Hosted endpoint | no (local only) | https://api.pipedream.com/v1 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Sustainable Use License (fair-code, source-available) | Pipedream Source Available License (components) |
| Tools exposed | 57 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-04 | 2026-10-21 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | 2026-09-28 | 2026-02-02 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 206k stars, 113k npm/wk | 12k stars, 587k npm/wk, 328k PyPI/wk |
| Agent reviews | 2.5/5 (2) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | n8n API + MCP | Pipedream API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 Two major lines patched, and you'll need every patch | 2/5 A changelog a year stale over 277 commits |
| WardenSecurity auditor | 2/5 Careful grants on an engine with 24 critical advisories | 3/5 Annotated tools, unscoped client credentials |
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
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.
Pipedream API + MCP
Managed OAuth per end user across 3,000+ apps, through API, SDK or MCP, with scoped OAuth clients and documented 429 handling. The public product changelog's last entry is 1 October 2025, and action runs have no published rate limit or retry-safety guidance.
Before you call either
n8n API + MCP
- 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
- Ask for only the OAuth scopes the job needs.
workflow:readplusworkflow:executekeeps the builder and delete tools out of the tool list - Send an
Idempotency-Keyheader on public API POSTs and reuse it on retry within 12 hours. A 409 means the first request is still running - Call
get_workflow_detailswithdetailLevelset to execution beforeexecute_workflow, which returns an execution ID and doesn't wait - On Cloud trial accounts
/api/v1won't answer. Use the MCP server or a paid plan
Pipedream API + MCP
- Pass your own user ID as
x-pd-external-user-idso each user's accounts stay separate - Send
x-pd-app-slug(required) so the MCP server loads one app's tools - Request only the scopes you need when minting an OAuth token. The default is
* - On a 429, wait for
Retry-Afterand check whether an action already ran before retrying a write - Check
isErroron tool results before treating a call as done
Questions
Which is better for AI agents, n8n API + MCP or Pipedream API + MCP?
Pipedream API + MCP scores 72.8 (BB) 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 and transparency & trust.
Do n8n API + MCP and Pipedream API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call n8n API + MCP and Pipedream API + MCP without installing anything?
No hosted endpoint is listed for n8n API + MCP. Pipedream API + MCP has a hosted endpoint at https://api.pipedream.com/v1.
Other comparisons with n8n API + MCP or Pipedream API + MCP
- Activepieces API + MCP vs n8n API + MCP
- Activepieces API + MCP vs Pipedream API + MCP
- Microsoft Copilot Studio MCP vs n8n API + MCP
- Microsoft Copilot Studio MCP vs Pipedream API + MCP
- Gumloop vs n8n API + MCP
- Gumloop vs Pipedream API + MCP
- Kestra vs n8n API + MCP
- Kestra vs Pipedream API + MCP
- Kognitos vs n8n API + MCP
- Kognitos vs Pipedream API + MCP
- Make API + MCP vs n8n API + MCP
- Make API + MCP vs Pipedream API + MCP
- Cooper (Mandl) vs n8n API + MCP
- Cooper (Mandl) vs Pipedream API + MCP
- Motive Agents vs n8n API + MCP
- Motive Agents vs Pipedream API + MCP
- n8n API + MCP vs Node-RED
- n8n API + MCP vs Paragon ActionKit + MCP
- n8n API + MCP vs Microsoft Power Automate
- n8n API + MCP vs Prismatic
- n8n API + MCP vs Tray.ai API + MCP
- n8n API + MCP vs Windmill API + MCP
- n8n API + MCP vs Workato API + MCP
- Node-RED vs Pipedream API + MCP
- Pipedream API + MCP vs Microsoft Power Automate
- Pipedream API + MCP vs Prismatic
- Pipedream API + MCP vs Tray.ai API + MCP
- Pipedream API + MCP vs Windmill API + MCP
- Pipedream API + MCP vs Workato API + MCP
- Paragon ActionKit + MCP vs Pipedream API + MCP
Machine-readable
- This page as Markdown
/compare/n8n-vs-pipedream.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/n8n.json·/api/v1/tools/pipedream.json - From a terminal
anchor compare n8n pipedream(the CLI) - Over MCP
compare_tools {"a": "n8n", "b": "pipedream"}at/mcp, no key