Head to head · Workflow automation · October 2026 research run
n8n API + MCP vs Tray.ai API + MCP
Tray.ai API + MCP scores 59.4 (C) on agent readiness against n8n API + MCP's 49.3 (D), and leads in 1 of 7 scored categories. n8n API + MCP leads on schema & documentation, agent ergonomics, payments & pricing, maintenance & community and transparency & trust. Both do workflow automation.
Best workflow automation platforms with APIs for AI agents · All 174 workflows 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 80
- Agent ergonomics, 79 against 33
- Payments & pricing, 45 against 30
- Maintenance & community, 80 against 60
- Transparency & trust, 87 against 69
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 SaaS vendors embedding integrations for their customers, with an agent that acts per end user.
Ahead on
- Reliability, 72 against 20
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
- No incidents deducted, where n8n API + MCP loses 15 points for them
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.
Reliability Tray.ai API + MCP +52
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.
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).
Agent ergonomics n8n API + MCP +46
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.
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).
Maintenance & community n8n API + MCP +20
n8n API + MCP 80
n8n@2.46.6, the stable tag, on 4 November 2026 (30). 134 tags on the 1.x and 2.x lines from 6 August to 4 November (112 on 2.x, 22 on 1.x), not counting experimental tags or the 3.0 and 3.1 early-access releases, and dated release notes for 2.35 to 2.46 (20). Issue handling per the 1 October check, not re-read on 4 November, since GitHub's pages answer 403 here (20). No official REST SDK, and the MCP server wasn't found in the official registry on 1 October (0). CI on master runs build, format, unit tests on Node 24 and 26 and lint, with SBOM and security workflows beside it (10). Total 80.
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).
Transparency & trust n8n API + MCP +18
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.
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).
Payments & pricing n8n 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.
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.
Schema & documentation n8n API + MCP +12
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.
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).
Score by category
| Category | Weight | n8n API + MCP | Tray.ai API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 20 | 72 | Tray.ai API + MCP +52 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 80 | n8n API + MCP +12 |
| Agent ergonomics | 13% | 79 | 33 | n8n API + MCP +46 |
| Security & auth | 14% | 70 | 66 | n8n API + MCP +4 |
| Payments & pricing | 10% | 45 | 30 | n8n API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 60 | n8n API + MCP +20 |
| Transparency & trust | 7% | 87 | 69 | n8n API + MCP +18 |
| Negative events | ≤15 | -15 | 0 | |
| Total | D 49.3/100 | C 59.4/100 |
Facts side by side
| Fact | n8n API + MCP | Tray.ai API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | n8n | Tray.ai |
| Hosted endpoint | no (local only) | 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 | Sustainable Use License (fair-code, source-available) | proprietary |
| Tools exposed | 57 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-04 | 2026-10-13 |
| Terms last updated | couldn't be read | 2025-01-28 |
| Privacy policy last updated | 2026-09-28 | 2026-01-01 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 206k stars, 113k npm/wk | none |
| 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 | n8n API + MCP | Tray.ai API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 Two major lines patched, and you'll need every patch | 3/5 Dated releases, and credentials that lapse in seven days |
| WardenSecurity auditor | 2/5 Careful grants on an engine with 24 critical advisories | 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
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.
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
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
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, n8n API + MCP or Tray.ai API + MCP?
Tray.ai API + MCP scores 59.4 (C) on agent readiness against n8n API + MCP's 49.3 (D), and leads in 1 of 7 scored categories. n8n API + MCP leads on schema & documentation, agent ergonomics, payments & pricing, maintenance & community and transparency & trust.
Do n8n 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 n8n API + MCP and Tray.ai API + MCP without installing anything?
No hosted endpoint is listed for n8n API + MCP. Tray.ai API + MCP has a hosted endpoint at https://api.tray.io/core/v1.
Other comparisons with n8n API + MCP or Tray.ai API + MCP
- Activepieces API + MCP vs n8n API + MCP
- Activepieces API + MCP vs Tray.ai API + MCP
- Microsoft Copilot Studio MCP vs n8n API + MCP
- Microsoft Copilot Studio MCP vs Tray.ai API + MCP
- Gumloop vs n8n API + MCP
- Gumloop vs Tray.ai API + MCP
- Kestra vs n8n API + MCP
- Kestra vs Tray.ai API + MCP
- Kognitos vs n8n API + MCP
- Kognitos vs Tray.ai API + MCP
- Make API + MCP vs n8n API + MCP
- Make API + MCP vs Tray.ai API + MCP
- Cooper (Mandl) vs n8n API + MCP
- Cooper (Mandl) vs Tray.ai API + MCP
- Motive Agents vs n8n API + MCP
- Motive Agents vs Tray.ai API + MCP
- n8n API + MCP vs Node-RED
- n8n API + MCP vs Paragon ActionKit + MCP
- n8n API + MCP vs Pipedream API + MCP
- n8n API + MCP vs Microsoft Power Automate
- n8n API + MCP vs Prismatic
- n8n API + MCP vs Windmill API + MCP
- n8n API + MCP vs Workato API + MCP
- Node-RED vs Tray.ai API + MCP
- Pipedream API + MCP vs Tray.ai 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 Tray.ai API + MCP
Machine-readable
- This page as Markdown
/compare/n8n-vs-tray.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/n8n.json·/api/v1/tools/tray.json - From a terminal
anchor compare n8n tray(the CLI) - Over MCP
compare_tools {"a": "n8n", "b": "tray"}at/mcp, no key