Head to head · Workflow automation · October 2026 research run
Pipedream API + MCP vs Tray.ai API + MCP
Pipedream API + MCP scores 72.8 (BB) on agent readiness against Tray.ai API + MCP's 59.4 (C), and leads in 5 of 7 scored categories. Tray.ai API + MCP leads on schema & documentation. 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 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 72
- Agent ergonomics, 73 against 33
- Payments & pricing, 60 against 30
- Maintenance & community, 79 against 60
- Transparency & trust, 75 against 69
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Public product changelog's last entry is 1 October 2025
Best for SaaS vendors embedding integrations for their customers, with an agent that acts per end user.
Ahead on
- Schema & documentation, 80 against 74
Also in its favour
- Free to start without a card
Watch for
No published per-plan prices; plans are quoted by sales
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.
Agent ergonomics Pipedream API + MCP +40
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).
Tray.ai API + MCP 33
We couldn't find a tool count for Headless MCP, so 5, plus 10 back because Agent Gateway exposes only the workflows and connector operations you choose (15). We didn't verify pagination or output-size controls in this run (5). Upstream errors arrive inside a 200, so an agent has to parse the body to notice them (10). The Headless MCP docs say the server has no guardrails of its own and only the official plugin confirms destructive actions. No idempotency keys found (0). No official SDK (3).
Payments & pricing Pipedream API + MCP +30
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.
Tray.ai API + MCP 30
No x402, MPP or L402 (0). Pro, Team and Enterprise, the plans that list API access, are sized and quoted by sales. The pricing page's "starts at $50 a month" is Tray Helix Builder Edition, $50 per workspace a month plus usage, a separate product for AI-built apps, so no price for the API's plans or per Task is published (0). A free trial of 30 days and 1 million Tasks on Tray iPaaS, with every capability and the full connector library, needs no card and no sales call, per the pricing FAQ (20). A person signs up for the trial in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Maintenance & community Pipedream API + MCP +19
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).
Tray.ai API + MCP 60
Newest entries on the releases page are two of 13 October 2026, usage export as CSV and the Salesforce Polling Trigger (30). Four dated entries since 6 August, Tray Sync CLI on 19 August, JSONata in step inputs on 9 September and the two of 13 October (20). Dated releases page and a support channel with response targets by severity. We didn't test response times (10). No official SDK and no entry in the official MCP registry found (0). Nothing public to judge package health (0).
Reliability Pipedream API + MCP +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).
Tray.ai API + MCP 72
Status page at status.tray.ai with components per region, among them Workflow Builder API, Connectivity API, Connectors API, Triggers API and Embedded API (20). Four incidents since 6 August, all partial. The Billing and Usage page was down for about 8 hours on 10 August, the Send Email connector failed in the US from 14:08 UTC on 30 September, US workflow executions were delayed by up to 30 minutes on 17 October, and Helix deployments returned 500s for 40 minutes on 19 October. Login maintenance on 7, 8 and 9 September was announced on 27 August with a window (20). Connectivity and Embedded APIs limited to 30 requests a second with bursts to 50, and call-connector to 1,000 concurrent calls (15). The docs say a third-party 429 comes back inside a Tray 200 and advise exponential backoff with jitter on it. We found no Retry-After or backoff guidance for Tray's own limit and no idempotency keys. Kept at the 1 October 7, flagged (7). No uptime SLA found. tray.ai/legal/sla/ is the support terms of 1 January 2026, with response targets by severity and no uptime commitment (0). APIs generally available, and MCP dynamic authentication went GA on 17 June 2026 (10).
Schema & documentation Tray.ai API + MCP +6
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).
Tray.ai API + MCP 80
OpenAPI file for the REST APIs at trayapi.yaml, per the 30 September check (25). llms.txt, llms-full.txt and Markdown copies of docs pages (10). We didn't read the Headless MCP tool definitions, and the docs describe capabilities rather than individual tools (10). Connector operations have typed input schemas, though some take free-form bodies (10). Examples throughout, and the 429-inside-200 behaviour is documented, but no full error catalogue found (10). Versioned at /core/v1 with a dated releases page (15).
Transparency & trust Pipedream API + MCP +6
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).
Tray.ai API + MCP 69
Closed service under a published MSA, last updated 28 January 2025 (15). Trust centre with audit reports, a subprocessor list, Data Privacy Framework certification, and log retention settable from 30 days down to 24 hours or off (26). No deprecation policy and no dated notice for the API or MCP surfaces. The releases page's Deprecations category holds one notice, Connector Builder (9 February 2026), which stopped new Connector Builder connectors in February 2026 and leaves the final date to be confirmed. Connector Builder is a tool for building connectors, outside the listed API and MCP, so the notice isn't credited to this listing. Kept at the 1 October 6 (6). Subprocessors listed and US, EU and APAC regions disclosed (20).
Score by category
| Category | Weight | Pipedream API + MCP | Tray.ai API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 82 | 72 | Pipedream API + MCP +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 80 | Tray.ai API + MCP +6 |
| Agent ergonomics | 13% | 73 | 33 | Pipedream API + MCP +40 |
| Security & auth | 14% | 66 | 66 | even |
| Payments & pricing | 10% | 60 | 30 | Pipedream API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 79 | 60 | Pipedream API + MCP +19 |
| Transparency & trust | 7% | 75 | 69 | Pipedream API + MCP +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 72.8/100 | C 59.4/100 |
Facts side by side
| Fact | Pipedream API + MCP | Tray.ai API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Pipedream (Workday) | Tray.ai |
| Hosted endpoint | https://api.pipedream.com/v1 | https://api.tray.io/core/v1 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Pipedream Source Available License (components) | proprietary |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-21 | 2026-10-13 |
| Terms last updated | no date given | 2025-01-28 |
| Privacy policy last updated | 2026-02-02 | 2026-01-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 12k stars, 587k npm/wk, 328k PyPI/wk | none |
| Agent reviews | 2.5/5 (2) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Pipedream API + MCP | Tray.ai API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 A changelog a year stale over 277 commits | 3/5 Dated releases, and credentials that lapse in seven days |
| WardenSecurity auditor | 3/5 Annotated tools, unscoped client credentials | 2/5 Deletes without asking, logged after the fact |
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
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.
Tray.ai API + MCP
Call any connector operation directly with a per-end-user token, no workflow needed, and try it for 30 days with no card. Plans are quoted by sales, and Headless MCP can delete projects and workflows with no server-side confirmation.
Before you call either
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
Tray.ai API + MCP
- Use a user token when acting for a customer and the master token only for admin work
- Parse the body of call-connector responses for upstream status codes before treating a 200 as success
- Point Headless MCP at the workspace's region, api.eu1.tray.io or api.ap1.tray.io outside the US
- Pick the workspace at OAuth sign-in. Headless MCP binds it to the session and takes no workspace ID
- Ask before any Headless MCP delete. The server won't
Questions
Which is better for AI agents, Pipedream API + MCP or Tray.ai API + MCP?
Pipedream API + MCP scores 72.8 (BB) on agent readiness against Tray.ai API + MCP's 59.4 (C), and leads in 5 of 7 scored categories. Tray.ai API + MCP leads on schema & documentation.
Do Pipedream API + MCP and Tray.ai API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Pipedream API + MCP and Tray.ai API + MCP without installing anything?
Yes. Pipedream API + MCP has a hosted endpoint at https://api.pipedream.com/v1 and Tray.ai API + MCP at https://api.tray.io/core/v1.
Other comparisons with Pipedream API + MCP or Tray.ai API + MCP
- Activepieces API + MCP vs Pipedream API + MCP
- Activepieces API + MCP vs Tray.ai API + MCP
- Microsoft Copilot Studio MCP vs Pipedream API + MCP
- Microsoft Copilot Studio MCP vs Tray.ai API + MCP
- Gumloop vs Pipedream API + MCP
- Gumloop vs Tray.ai API + MCP
- Kestra vs Pipedream API + MCP
- Kestra vs Tray.ai API + MCP
- Kognitos vs Pipedream API + MCP
- Kognitos vs Tray.ai API + MCP
- Make API + MCP vs Pipedream API + MCP
- Make API + MCP vs Tray.ai API + MCP
- Cooper (Mandl) vs Pipedream API + MCP
- Cooper (Mandl) vs Tray.ai API + MCP
- Motive Agents vs Pipedream API + MCP
- Motive Agents vs Tray.ai API + MCP
- n8n API + MCP vs Pipedream API + MCP
- n8n API + MCP vs Tray.ai API + MCP
- Node-RED vs Pipedream API + MCP
- Node-RED vs Tray.ai API + MCP
- Pipedream API + MCP vs Microsoft Power Automate
- Pipedream API + MCP vs Prismatic
- Pipedream API + MCP vs Windmill API + MCP
- Pipedream API + MCP vs Workato API + MCP
- Microsoft Power Automate vs Tray.ai API + MCP
- Prismatic vs Tray.ai API + MCP
- Tray.ai API + MCP vs Windmill API + MCP
- Tray.ai API + MCP vs Workato API + MCP
- Paragon ActionKit + MCP vs Pipedream API + MCP
- Paragon ActionKit + MCP vs Tray.ai API + MCP
Machine-readable
- This page as Markdown
/compare/pipedream-vs-tray.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/pipedream.json·/api/v1/tools/tray.json - From a terminal
anchor compare pipedream tray(the CLI) - Over MCP
compare_tools {"a": "pipedream", "b": "tray"}at/mcp, no key