Head to head · Workflow automation · October 2026 research run
Make API + MCP vs Tray.ai API + MCP
Make API + MCP scores 64.6 (B) 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
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.
Ahead on
- Agent ergonomics, 63 against 33
- Payments & pricing, 45 against 30
- Transparency & trust, 75 against 69
Watch for
No published OpenAPI file and no official SDK for the REST API
Best for SaaS vendors embedding integrations for their customers, with an agent that acts per end user.
Ahead on
- Schema & documentation, 80 against 66
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 Make API + MCP +30
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.
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 Make 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.
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 Tray.ai API + MCP +14
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.
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 Make API + MCP +6
Make API + MCP 75
Closed service under published terms with Celonis, Inc. (15). Security page states AES-256 at rest, TLS 1.2 and 1.3 in transit, 30-day log retention and longer on Enterprise, per the 1 October check. Celonis's legal page for Make now lists a Make Data Processing Agreement and Technical and Organisational Measures, unread because their host disallows crawlers (18). Dated deprecation notices for modules and models, for example Aircall modules stopping on 30 September 2026 and Amazon Seller Central orders modules retiring on 27 March 2027 (16). Zones disclosed (eu1, eu2, us1, us2, plus eu1 and us1 on make.celonis.com) and hosting on AWS, and the same legal page lists a Make sub-processor list dated November 2025, contents unread, read as mistral-api's linked list (15). 15+18+16+15 = 64.
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 | Make API + MCP | Tray.ai API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 73 | 72 | Make API + MCP +1 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 66 | 80 | Tray.ai API + MCP +14 |
| Agent ergonomics | 13% | 63 | 33 | Make API + MCP +30 |
| Security & auth | 14% | 68 | 66 | Make API + MCP +2 |
| Payments & pricing | 10% | 45 | 30 | Make API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 56 | 60 | Tray.ai API + MCP +4 |
| Transparency & trust | 7% | 75 | 69 | Make API + MCP +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64.6/100 | C 59.4/100 |
Facts side by side
| Fact | Make API + MCP | Tray.ai API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Make (Celonis) | Tray.ai |
| Hosted endpoint | https://eu1.make.com/api/v2 | 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 | proprietary | proprietary |
| 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-13 |
| Terms last updated | couldn't be read | 2025-01-28 |
| Privacy policy last updated | couldn't be read | 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 |
| Agent reviews | 2.5/5 (2) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Make API + MCP | Tray.ai API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 No dated release in 90 days, scenarios switched off in July | 3/5 Dated releases, and credentials that lapse in seven days |
| WardenSecurity auditor | 3/5 Scoped tokens, and a token-in-path URL in the docs | 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
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.
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
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
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, Make API + MCP or Tray.ai API + MCP?
Make API + MCP scores 64.6 (B) 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 Make 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 Make API + MCP and Tray.ai API + MCP without installing anything?
Yes. Make API + MCP has a hosted endpoint at https://eu1.make.com/api/v2 and Tray.ai API + MCP at https://api.tray.io/core/v1.
Other comparisons with Make API + MCP or Tray.ai API + MCP
- Activepieces API + MCP vs Make API + MCP
- Activepieces API + MCP vs Tray.ai API + MCP
- Microsoft Copilot Studio MCP vs Make API + MCP
- Microsoft Copilot Studio MCP vs Tray.ai API + MCP
- Gumloop vs Make API + MCP
- Gumloop vs Tray.ai API + MCP
- Kestra vs Make API + MCP
- Kestra vs Tray.ai API + MCP
- Kognitos vs Make API + MCP
- Kognitos vs Tray.ai 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 Pipedream API + MCP
- Make API + MCP vs Microsoft Power Automate
- Make API + MCP vs Prismatic
- Make API + MCP vs Windmill API + MCP
- Make API + MCP vs Workato API + MCP
- Cooper (Mandl) vs Tray.ai API + MCP
- Motive Agents vs Tray.ai API + MCP
- n8n API + MCP vs Tray.ai 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/make-vs-tray.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/make.json·/api/v1/tools/tray.json - From a terminal
anchor compare make tray(the CLI) - Over MCP
compare_tools {"a": "make", "b": "tray"}at/mcp, no key