Head to head · Workflow automation · October 2026 research run
Make API + MCP vs Pipedream API + MCP
Pipedream API + MCP scores 72.8 (BB) on agent readiness against Make API + MCP's 64.6 (B), and leads in 5 of 7 scored categories. 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 Teams who build in a visual editor and want an agent to run those scenarios as tools, cloud only.
Also in its favour
- Free to start without a card
Watch for
No published OpenAPI file and no official SDK for the REST API
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 73
- Schema & documentation, 74 against 66
- Agent ergonomics, 73 against 63
- Payments & pricing, 60 against 45
- Maintenance & community, 79 against 56
Also in its favour
- Agent-ready, a grade of BB or better
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.
Maintenance & community Pipedream API + MCP +23
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.
Pipedream API + MCP 79
TypeScript SDK v3.3.0 and Python SDK v2.3.0 tagged on 21 October 2026, 11 days before this check (30). In the 90 days from 3 August the TypeScript SDK tagged v3.1.3 (18 August), v3.1.4, v3.1.5, v3.1.6, v3.2.0 and v3.3.0, and the Python SDK v2.1.19, v2.1.20, v2.2.0 and v2.3.0 (20). The public product changelog hasn't moved since 1 October 2025, though the components repository took 261 commits from 3 August to 30 October 2026 (7). Current official SDKs in TypeScript, Python and Java (15). SDKs are generated with Fern and the components repository has CI, but we didn't confirm test runs (7).
Payments & pricing Pipedream API + MCP +15
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.
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.
Agent ergonomics Pipedream API + MCP +10
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.
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).
Reliability Pipedream API + MCP +9
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.
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 Pipedream API + MCP +8
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.
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).
Score by category
| Category | Weight | Make API + MCP | Pipedream API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 73 | 82 | Pipedream API + MCP +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 66 | 74 | Pipedream API + MCP +8 |
| Agent ergonomics | 13% | 63 | 73 | Pipedream API + MCP +10 |
| Security & auth | 14% | 68 | 66 | Make API + MCP +2 |
| Payments & pricing | 10% | 45 | 60 | Pipedream API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 56 | 79 | Pipedream API + MCP +23 |
| Transparency & trust | 7% | 75 | 75 | even |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64.6/100 | BB 72.8/100 |
Facts side by side
| Fact | Make API + MCP | Pipedream API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Make (Celonis) | Pipedream (Workday) |
| Hosted endpoint | https://eu1.make.com/api/v2 | 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 | proprietary | Pipedream Source Available License (components) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.make/mcp-server | not listed |
| Last release | 2026-10-06 | 2026-10-21 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | 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 | none | 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 rate them the same.
| Reviewer | Make API + MCP | Pipedream API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 No dated release in 90 days, scenarios switched off in July | 2/5 A changelog a year stale over 277 commits |
| WardenSecurity auditor | 3/5 Scoped tokens, and a token-in-path URL in the docs | 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
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.
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
Make API + MCP
- Find the organisation's zone first. It may be on make.com or make.celonis.com
- Set scenarios to on-demand scheduling so the MCP server lists them as tools
- Use the header form at
/mcp/v2rather than the/mcp/u/<key>/v2path form - On a 429, wait a full minute before retrying. The limit is per minute and no Retry-After is sent
- If a scenario tool call times out, keep the returned
executionIdand fetch the result later; scenarios run for up to 40 minutes
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, Make API + MCP or Pipedream API + MCP?
Pipedream API + MCP scores 72.8 (BB) on agent readiness against Make API + MCP's 64.6 (B), and leads in 5 of 7 scored categories.
Do Make API + MCP and Pipedream API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Make API + MCP and Pipedream API + MCP without installing anything?
Yes. Make API + MCP has a hosted endpoint at https://eu1.make.com/api/v2 and Pipedream API + MCP at https://api.pipedream.com/v1.
Other comparisons with Make API + MCP or Pipedream API + MCP
- Activepieces API + MCP vs Make API + MCP
- Activepieces API + MCP vs Pipedream API + MCP
- Microsoft Copilot Studio MCP vs Make API + MCP
- Microsoft Copilot Studio MCP vs Pipedream API + MCP
- Gumloop vs Make API + MCP
- Gumloop vs Pipedream API + MCP
- Kestra vs Make API + MCP
- Kestra vs Pipedream API + MCP
- Kognitos vs Make API + MCP
- Kognitos vs Pipedream API + MCP
- Make API + MCP vs Cooper (Mandl)
- Make API + MCP vs Motive Agents
- Make API + MCP vs n8n API + MCP
- Make API + MCP vs Node-RED
- Make API + MCP vs Paragon ActionKit + MCP
- Make API + MCP vs Microsoft Power Automate
- Make API + MCP vs Prismatic
- Make API + MCP vs Tray.ai API + MCP
- Make API + MCP vs Windmill API + MCP
- Make API + MCP vs Workato API + MCP
- Cooper (Mandl) vs Pipedream API + MCP
- Motive Agents vs Pipedream API + MCP
- n8n API + MCP vs Pipedream 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/make-vs-pipedream.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/make.json·/api/v1/tools/pipedream.json - From a terminal
anchor compare make pipedream(the CLI) - Over MCP
compare_tools {"a": "make", "b": "pipedream"}at/mcp, no key