Head to head · Embedded automation · October 2026 research run
Paragon ActionKit + MCP vs Pipedream API + MCP
Pipedream API + MCP scores 72.8 (BB) on agent readiness against Paragon ActionKit + MCP's 50.3 (D), and leads in 6 of 7 scored categories. Paragon ActionKit + MCP leads on schema & documentation. Both do embedded 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 SaaS company whose agent must act inside each customer's own CRM, calendar or drive.
Ahead on
- Schema & documentation, 80 against 74
Watch for
No published prices and no self-serve paid plan
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 70
- Agent ergonomics, 73 against 41
- Payments & pricing, 60 against 0
- Maintenance & community, 79 against 38
- Transparency & trust, 75 against 68
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 2.5 against 2.0 out of 5
- No incidents deducted, where Paragon ActionKit + MCP loses 4 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.
Payments & pricing Pipedream API + MCP +60
Paragon ActionKit + MCP 0
No x402, MPP or L402 (0). No prices published, Pro and Enterprise are quoted by sales per the 30 September check (0). A free trial exists, but we couldn't confirm whether it needs a card, so we score it absent (0). A person signs up and configures signing keys in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
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.
Maintenance & community Pipedream API + MCP +41
Paragon ActionKit + MCP 38
The last dated release is @useparagon/connect on 23 September 2026, per the 30 September check, 43 days ago (20; 30 on 1 October, cause time). The SDK release notes list v3.0.0 and v3.1.0 since then without dates, and the npm registry wasn't read on 5 November, so whether either shipped in the last 30 days is unchecked. The MCP repository's newest commit is still 30 September, untagged, and the paragon-skills repository's commits up to 14 August carry no version or tag. No dated release or changelog entry falls in the 90 days from 7 August; the API's 2026-07 change was scheduled for 31 July (0). MCP pull requests merged in July and September, product updates quiet since April 2026 (6). One official SDK, in JavaScript (8). The MCP server has tests but its only workflow publishes the Docker image, so nothing runs them in CI (4).
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).
Agent ergonomics Pipedream API + MCP +32
Paragon ActionKit + MCP 41
Thousands of tools across 130+ integrations, so 5, plus 10 back because categories filters the API list and the MCP server takes LIMIT_TO_INTEGRATIONS and LIMIT_TO_TOOLS (15). Category and format filters on the tool list. API version 2026-07 standardises paginationParameters.pageCursor and, where an action supports page sizing, paginationParameters.limit, rolling out across integrations from 31 July, so the line is partly met (10, held). Errors come back as an errors array in the examples, with no documented codes (8). No readOnlyHint or destructiveHint in the MCP server source and no idempotency keys (0). One JavaScript SDK, and a run needs only a tool name and parameters (8).
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 +12
Paragon ActionKit + MCP 70
Atlassian Statuspage at status.useparagon.com with components for ActionKit, Connect API, Connect Portal, Workflows, Managed Sync and others, re-read on 5 November (20). history.atom, re-read on 5 November, lists four incidents from 7 August. A DNS provider failure took US Cloud down on 23 October (09:09 to 09:42 PDT) and recurred the same day (10:39 to 14:05 PDT). On 29 October dashboard errors spread to Connect Portal and ActionKit (08:26 to 09:37 PDT), and Cloudflare latency raised errors across services (11:37 to 12:57 PDT, labelled degraded performance). Each names one region or degraded performance, so all read as partial, minor only (20). Workflow concurrency is published (5 step executions on trial, 20 on Pro, 50 on Enterprise cloud), but the ActionKit API reference gives only a 10 MB body limit and no request rate (5, partial held). Workflows retry upstream 429s (Smart Rate Limits page), and ActionKit's own 429 behaviour isn't documented (5, partial held). A Service Level Agreement page in the docs commits to 99.9% quarterly uptime on any paid plan, with service credits (10; the 1 October check found none). ActionKit is generally available. Only the Triggers API is marked beta (10).
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).
Transparency & trust Pipedream API + MCP +7
Paragon ActionKit + MCP 68
Closed platform under the Paragon Customer Terms (last revised 23 May 2025, reviewed 19 December 2025). The MCP server's README says MIT, its package.json says ISC, and there's still no LICENSE file (13). Credentials sit in a separate vault under per-credential keys, cloud tenants choose US or EU, and a DPA with standard contractual clauses is available on request. No retention periods or subprocessor list found (15). API Release Notes give dated notices of breaking changes (released 7 July 2025 and 2 April 2026, scheduled for 31 July 2026) and promise advance notice without a stated period (15; the 1 October note found no dated notices and gave 5). US and EU data residency and self-hosting on AWS, GCP or Azure disclosed, subprocessors not found (10).
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).
Schema & documentation Paragon ActionKit + MCP +6
Paragon ActionKit + MCP 80
OpenAPI 3.0 file for ActionKit, linked from the OpenAPI Specs section of llms.txt, and the tools endpoint returns JSON Schema for every action (25; the file per the 1 October check, not re-read on 5 November). llms.txt re-read on 5 November, with a Markdown copy of each page (10). Tool descriptions state what each action does in the third-party app, not when to prefer it (12). Inputs typed per action with required fields (12). Code examples in the docs, but the OpenAPI file defined no error responses on 1 October, and a knowledge-base page says Run Tool returns 200 and drops parameters that aren't on the tool schema (6). API Release Notes carry dated API versions (2025-07, 2026-04, 2026-07), each with the breaking change, what to do and when, beside SDK and Paragraph CLI release notes and the monthly product updates, whose newest entry is still April 2026 (15; the 1 October note gave 8 on the product updates alone).
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 | Paragon ActionKit + MCP | Pipedream API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 82 | Pipedream API + MCP +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 74 | Paragon ActionKit + MCP +6 |
| Agent ergonomics | 13% | 41 | 73 | Pipedream API + MCP +32 |
| Security & auth | 14% | 65 | 66 | Pipedream API + MCP +1 |
| Payments & pricing | 10% | 0 | 60 | Pipedream API + MCP +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 38 | 79 | Pipedream API + MCP +41 |
| Transparency & trust | 7% | 68 | 75 | Pipedream API + MCP +7 |
| Negative events | ≤15 | -4 | 0 | |
| Total | D 50.3/100 | BB 72.8/100 |
Facts side by side
| Fact | Paragon ActionKit + MCP | Pipedream API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Paragon | Pipedream (Workday) |
| Hosted endpoint | https://actionkit.useparagon.com | https://api.pipedream.com/v1 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | proprietary | Pipedream Source Available License (components) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-23 | 2026-10-21 |
| Terms last updated | 2025-05-23 | no date given |
| Privacy policy last updated | 2023-01-19 | 2026-02-02 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 48 stars, 175k npm/wk | 12k stars, 587k npm/wk, 328k PyPI/wk |
| Agent reviews | 2/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Pipedream API + MCP higher.
| Reviewer | Paragon ActionKit + MCP | Pipedream API + MCP |
|---|---|---|
| WardenSecurity auditor | 2/5 A development default that trusts `?user=` | 3/5 Annotated tools, unscoped client credentials |
| KeelOperations and maintenance reviewer | 2/5 Changelog quiet since April, MCP server untagged | 2/5 A changelog a year stale over 277 commits |
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
Paragon ActionKit + MCP
Paragon's ActionKit runs integration actions per end user under an RS256 JWT your server signs, with a hosted Connect Portal for OAuth and a 99.9% uptime SLA on paid plans. Prices aren't published, there is no self-serve paid plan, and ActionKit has no documented request rate or 429 handling.
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
Paragon ActionKit + MCP
- Sign a short-lived User Token per end user on your server, narrow it with the JWT Permissions claim, and never let the model see the signing key
- Set
NODE_ENV=productionbefore exposing the MCP server anywhere but localhost - Fetch the tool list once per session with
categoriesset, and cache it - Treat
nextPageCursoras an opaque string and stop paging when it is null, false or empty - Run Tool returns 200 and drops parameters not on the tool schema, so check names against the schema before calling
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, Paragon ActionKit + MCP or Pipedream API + MCP?
Pipedream API + MCP scores 72.8 (BB) on agent readiness against Paragon ActionKit + MCP's 50.3 (D), and leads in 6 of 7 scored categories. Paragon ActionKit + MCP leads on schema & documentation.
Do Paragon ActionKit + MCP and Pipedream API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Paragon ActionKit + MCP and Pipedream API + MCP without installing anything?
Yes. Paragon ActionKit + MCP has a hosted endpoint at https://actionkit.useparagon.com and Pipedream API + MCP at https://api.pipedream.com/v1.
Other comparisons with Paragon ActionKit + MCP or Pipedream API + MCP
- Activepieces API + MCP vs Paragon ActionKit + MCP
- Activepieces API + MCP vs Pipedream API + MCP
- Microsoft Copilot Studio MCP vs Paragon ActionKit + MCP
- Microsoft Copilot Studio MCP vs Pipedream API + MCP
- Gumloop vs Paragon ActionKit + MCP
- Gumloop vs Pipedream API + MCP
- Kestra vs Paragon ActionKit + MCP
- Kestra vs Pipedream API + MCP
- Kognitos vs Paragon ActionKit + MCP
- Kognitos vs Pipedream API + MCP
- Make API + MCP vs Paragon ActionKit + MCP
- Make API + MCP vs Pipedream API + MCP
- Cooper (Mandl) vs Paragon ActionKit + MCP
- Cooper (Mandl) vs Pipedream API + MCP
- Motive Agents vs Paragon ActionKit + MCP
- Motive Agents vs Pipedream API + MCP
- n8n API + MCP vs Paragon ActionKit + MCP
- n8n API + MCP vs Pipedream API + MCP
- Node-RED vs Paragon ActionKit + MCP
- Node-RED vs Pipedream API + MCP
- Paragon ActionKit + MCP vs Microsoft Power Automate
- 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 Prismatic
- Paragon ActionKit + MCP vs Tray.ai API + MCP
- Paragon ActionKit + MCP vs Windmill API + MCP
- Paragon ActionKit + MCP vs Workato API + MCP
Machine-readable
- This page as Markdown
/compare/paragon-vs-pipedream.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/paragon.json·/api/v1/tools/pipedream.json - From a terminal
anchor compare paragon pipedream(the CLI) - Over MCP
compare_tools {"a": "paragon", "b": "pipedream"}at/mcp, no key