Head to head · Workflow automation · October 2026 research run

Tray.ai API + MCP vs Windmill API + MCP

Tray.ai API + MCP scores 59.4 (C) on agent readiness against Windmill API + MCP's 48 (D), and leads in 3 of 7 scored categories. Windmill API + MCP leads on 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

Tray.ai API + MCP C

Best for SaaS vendors embedding integrations for their customers, with an agent that acts per end user.

Ahead on

  • Reliability, 72 against 15
  • Security & auth, 66 against 60

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Windmill API + MCP loses 11 points for them

Watch for

No published per-plan prices; plans are quoted by sales

Windmill API + MCP D

Best for Engineering teams who'd rather write steps in Python, TypeScript, Go or SQL and expose them as tools.

Ahead on

  • Agent ergonomics, 73 against 33
  • Payments & pricing, 53 against 30
  • Maintenance & community, 87 against 60
  • Transparency & trust, 75 against 69

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

The default MCP URL puts the token in ?token= unless a superadmin turns that off

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 +57

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).

Windmill API + MCP 15

Read with the hosted lines. status.windmill.dev redirects to an UptimeRobot page. The page draws its services and history from stats.uptimerobot.com/api/, which that host's robots.txt closes, and the HTML read on 4 November shows only an error fetching the data, so no component or history was read and the status-page line has no evidence (0). No readable history (5, our limit rather than a finding against Windmill). No API request limit or 429 guidance published. Concurrency limits exist but you set them per script (0 and 0). The Enterprise plan lists SLA and priority support with a 3-hour response time, and no uptime SLA document was found, so the listed SLA has nothing behind it to read (0). The API and MCP server are generally available (10).

Agent ergonomics Windmill API + MCP +40

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).

Windmill API + MCP 73

42 endpoint tools plus one tool per exposed script and flow, so 5, plus 10 back because tokens can be limited to folders or favourites and to one workspace (15). Page and per_page on list endpoints, with filters on jobs (18). Errors come back as text messages, mostly undocumented in the spec (10). Annotations are set from the HTTP method, GET read-only and DELETE destructive, and every POST is marked destructive whether it is or not. No idempotency keys (15). Few required parameters, and Apache-2.0 clients for TypeScript, Python, Go and Rust (15).

Maintenance & community Windmill API + MCP +27

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).

Windmill API + MCP 87

v1.860.0 released on 3 November 2026, 1 day before this check (30). 100 dated changelog releases from 1.781.1 (6 August) to 1.860.0 (20). Open issues per the 1 October check, not re-read on 4 November, 569 open, most of the ten newest unlabelled (12). Official clients on npm (windmill-client) and PyPI (wmill) published by release workflows in the repository (15). CI runs backend tests on Linux and Windows, frontend checks, CLI and SDK tests (10).

Payments & pricing Windmill API + MCP +23

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.

Windmill API + MCP 53

No x402, MPP or L402 (0). Seat and worker prices are public ($20 a developer, $10 an operator, $50 a standard worker a month) but there's no per-execution price (15). Cloud free workspaces and the self-hosted Community Edition both run unlimited executions without a card (20). A person signs up or deploys an instance (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Security & auth Tray.ai API + MCP +6

Tray.ai API + MCP 66

Org master token for admin work and per-end-user user tokens, both bearer. Headless MCP signs in with OAuth2 bound to one workspace, and Agent Gateway takes OAuth2 or an API token. The master token can do everything in the org (22). User tokens confine calls to one end user's auths, but Headless MCP can delete projects, workflows and auths with no server-side confirmation (8). Connector results are untrusted third-party data and we found no injection guidance (3). Every action is logged and can be streamed to your own systems, MCP tool runs appear in the Monitor tab per the 30 September check, and log masking hides sensitive fields (15). SOC 1 and SOC 2 Type 2 (audit period to 31 July 2025, the 2025 to 2026 examination underway), HIPAA, an annual penetration test most recently on 23 September 2026, a bug bounty and a trust centre. security.txt answers 404 on 4 November (18).

Windmill API + MCP 60

Tokens take scopes down to a path (jobs:run:scripts:u/admin/my_script), carry an expiry and can be revoked, and MCP signs in with OAuth where the user picks the scope (30). Less 10 because the documented default MCP URL still carries the token as ?token= on 4 November, which superadmins can switch off (20). Read-only scopes and folder filters limit what the agent sees, with no confirmation step before destructive tools (14). The MCP docs explain that identity read from request headers can't be forged by prompt injection, but say nothing about untrusted script output (8). Audit logs on Enterprise per the pricing page, and job logs for every run on every edition (12). No SECURITY.md in the repository and no security.txt found. The release lifecycle page says advisories are published as GitHub Security Advisories and that Enterprise customers are told of CVEs by email, with no reporting route. Several 2026 CVEs reached the public through VulnCheck or another third party rather than a Windmill advisory. No SOC 2 report found (6).

Transparency & trust Windmill API + MCP +6

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).

Windmill API + MCP 75

AGPL-3.0 core and Apache-2.0 clients and OpenAPI, while the Community Edition images also contain proprietary code. The LICENSE file says which is which (25). The privacy policy (effective date given as 09/02/2026) covers windmill.dev, says data is kept only as long as necessary and names no periods or subprocessors, and the free edition keeps job details up to 30 days (10). The release lifecycle page says every release is backward compatible, each major version is supported for 24 months after the next one, and an end of life gets 12 months' notice (20). Usage stats are on by default. The self-hosted licence terms (effective 21 July 2026, clause 3.5) and the instance settings page list what is sent, and the settings page has a switch to turn it off. The stats code is closed source, so the list can't be checked against the code (15).

Score by category

CategoryWeightTray.ai API + MCPWindmill API + MCPEdge
Reliability16%7215Tray.ai API + MCP +57
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8079Tray.ai API + MCP +1
Agent ergonomics13%3373Windmill API + MCP +40
Security & auth14%6660Tray.ai API + MCP +6
Payments & pricing10%3053Windmill API + MCP +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6087Windmill API + MCP +27
Transparency & trust7%6975Windmill API + MCP +6
Negative events≤150-11
TotalC 59.4/100D 48/100

Facts side by side

FactTray.ai API + MCPWindmill API + MCP
KindHTTP APIHTTP API
VendorTray.aiWindmill Labs
Hosted endpointhttps://api.tray.io/core/v1https://app.windmill.dev/api
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceproprietaryAGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only parts
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-132026-11-03
Terms last updated2025-01-28not read yet
Privacy policy last updated2026-01-01no date given
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularitynone18k stars, 126k npm/wk, 218k PyPI/wk
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Windmill API + MCP higher, the other way from the total score.

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

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.

Windmill API + MCP

Token scopes reach a single script path with expiry, and a release ships most days under a published backward-compatibility policy. The default MCP URL puts the token in ?token= unless a superadmin turns that off, and ten CVEs were published in the past 12 months, several only by third parties.

Before you call either

Tray.ai API + MCP

  1. Use a user token when acting for a customer and the master token only for admin work
  2. Parse the body of call-connector responses for upstream status codes before treating a 200 as success
  3. Point Headless MCP at the workspace's region, api.eu1.tray.io or api.ap1.tray.io outside the US
  4. Pick the workspace at OAuth sign-in. Headless MCP binds it to the session and takes no workspace ID
  5. Ask before any Headless MCP delete. The server won't

Windmill API + MCP

  1. Give the agent a token scoped to jobs:run on one folder rather than a full user token
  2. Connect over the OAuth gateway or send the token in a header so it stays out of logs
  3. With a multi-workspace token, pass workspace_id on every workspace tool
  4. Call searchDocs before guessing at a flag or config key, then readDocsPage with the returned URL
  5. Poll the job by ID after runScriptByPath for long jobs instead of waiting on the call
  6. On self-hosted Community Edition, turn off telemetry in instance settings if the base URL and usage counts must stay private

Questions

Which is better for AI agents, Tray.ai API + MCP or Windmill API + MCP?

Tray.ai API + MCP scores 59.4 (C) on agent readiness against Windmill API + MCP's 48 (D), and leads in 3 of 7 scored categories. Windmill API + MCP leads on agent ergonomics, payments & pricing, maintenance & community and transparency & trust.

Do Tray.ai API + MCP and Windmill API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Tray.ai API + MCP and Windmill API + MCP without installing anything?

Yes. Tray.ai API + MCP has a hosted endpoint at https://api.tray.io/core/v1 and Windmill API + MCP at https://app.windmill.dev/api.

Are Tray.ai API + MCP and Windmill API + MCP open source?

No open-source release is listed for Tray.ai API + MCP. Windmill API + MCP is open source (AGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only parts).

Other comparisons with Tray.ai API + MCP or Windmill API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.