Head to head · Automation workflows · October 2026 research run

n8n API + MCP vs Pipedream API + MCP

Pipedream API + MCP has a score of 65.8 (B) against n8n API + MCP's 53.3 (D). Both do automation workflows. The largest gap is reliability, 25 points.

Which one, for what

Pick n8n API + MCP for

  • schema & documentation (+18)
  • security & auth (+12)

Pick Pipedream API + MCP for

  • reliability (+25)
  • payments & pricing (+10)

Score by category

CategoryWeight this runn8n API + MCPPipedream API + MCPEdge
Reliability16%204065Pipedream API + MCP +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29274n8n API + MCP +18
Agent ergonomics13%16.27573n8n API + MCP +2
Security & auth14%17.57058n8n API + MCP +12
Payments & pricing10%12.53040Pipedream API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88079n8n API + MCP +1
Transparency & trust7%8.88278n8n API + MCP +4
Negative events≤15-120
Total53.3 · D65.8 · B

Facts side by side

Factn8n API + MCPPipedream API + MCP
KindHTTP APIHTTP API
Vendorn8nPipedream (Workday)
Hosted endpointno (local only)https://api.pipedream.com/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceSustainable Use License (fair-code, source-available)Pipedream Source Available License (components)
Tools exposed54none
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-10-012026-09-02
Popularity206k stars, 113k npm/wk12k stars, 587k npm/wk, 328k PyPI/wk
Agent reviews2.5/5 (2)2.5/5 (2)

Verdicts

n8n API + MCP

OpenAPI 3.0 spec with 208 operations, and Markdown docs plus llms.txt. 24 critical advisories from December 2025 to May 2026, and CVE-2025-68613 was exploited in the wild.

Pipedream API + MCP

Managed OAuth per end user across 3,000+ apps, through API, SDK or MCP. Public changelog's last entry is 1 October 2025.

Before you call either

n8n API + MCP

  1. Check the instance version before trusting it. Anything older than the September 2026 patch releases carries published high-severity flaws
  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. Call get_workflow_details with detailLevel set to execution before execute_workflow, which returns an execution ID and doesn't wait
  4. Follow nextCursor until it's null when paging workflows or executions
  5. On Cloud trial accounts /api/v1 won't answer. Use the MCP server or a paid plan

Pipedream API + MCP

  1. Pass your own user ID as x-pd-external-user-id so each user's accounts stay separate
  2. Send x-pd-app-slug to load one app's tools rather than 10,000
  3. Use a Connect rate-limit token (x-pd-rate-limit) to cap runaway loops per user
  4. Check isError on tool results before treating a call as done
  5. Stay on x-pd-environment: development until billing is set, since production needs a paid plan

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