Head to head · Workflow automation · October 2026 research run

Windmill API + MCP vs Workato API + MCP

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

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

  • Schema & documentation, 79 against 61
  • Agent ergonomics, 73 against 55
  • Payments & pricing, 53 against 45
  • Maintenance & community, 87 against 60
  • Transparency & trust, 75 against 70

Also in its favour

  • Open source

Watch for

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

Workato API + MCP C

Best for Large companies that already run Workato and want agents inside its governance (roles, audit, per-user credentials).

Ahead on

  • Reliability, 65 against 15
  • Security & auth, 68 against 60

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

No 429, Retry-After or backoff guidance in the Developer API docs

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 Workato API + MCP +50

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

Workato API + MCP 65

Statuspage at status.workato.com with components and history, history.atom re-read on 4 November (20). The feed has 16 incidents from 6 August to 4 November. None is a major. Most are single connectors or one function (Salesforce on 12 August and 16 September, Box, QuickBooks, Databricks, SQL Transformations, AI by Workato actions, Genie and AIRO chats in the web app). The platform ones are partial. FileStorage was intermittently slow from 21 to 23 September with some API Platform steps timing out, the 8 October "errors or delays" ran from 07:51 to 08:24 PDT, log processing dropped some Logs page, audit-streaming and API traffic mirroring entries for about three hours on 20 October, and webhook ingestion was delayed on 30 October. Partial incidents read as minor (20). The Developer API quota page gives numbers per resource, for example 60 requests a minute on most endpoints, 1 a second for repeat, cancel and force-run, and 500 an hour for package imports (15). The response-code list stops at 400, 401, 403, 404 and 500, and no 429, Retry-After or backoff guidance was found on the API overview or quota page (0; the 3 carried from 1 October isn't a checklist value). No SLA in the terms or elsewhere found (0). Developer API and AIRO MCP are generally available (10). 20+20+15+0+0+10 = 65.

Maintenance & community Windmill API + MCP +27

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

Workato API + MCP 60

Newest changelog entries 3 November (October community connectors) and 20 October 2026 (shorter API Platform tokens) (30). More than three dated entries from 6 August, including 6 October (OAuth for MCP proxy servers), 14 October (on-prem agent 33.1) and 9 September (Event Streams payloads to 10 MB) (20). Public changelog and a support portal; responses not tested (10 of 15). No official SDK on npm or PyPI and no entry in the official MCP registry found. The Platform CLI's newest tag is 1.0.6 (26 March 2026), outside both windows (0). Nothing public to judge package health for an SDK (0). 30+20+10+0+0 = 60.

Schema & documentation Windmill API + MCP +18

Windmill API + MCP 79

OpenAPI 3.0.3 file in the repository with 947 operations on 4 November, versioned with each release (1.860.0) and Apache-2.0 licensed. Every script and flow gets a JSON Schema from its signature (25). llms.txt, read on 4 November, and searchDocs and readDocsPage hand the model Markdown docs from inside the MCP server (10). The 42 endpoint tools reuse OpenAPI summaries. The docs tools say when to call them, most others only say what they do (14). Typed parameters with required fields, but flow bodies are OpenFlow objects of nested free-form values (11). Per the 1 October count, 846 response entries are 200s and only about 30 document an error code (6). A release-please CHANGELOG with every release dated, and breaking changes flagged in it, though the API path itself isn't versioned (13).

Workato API + MCP 61

No OpenAPI file in the API docs. The Workato Platform CLI repository (workato-devs/workato-platform-cli) carries workato-api-spec.yaml, OpenAPI 3.0.3 with 38 operations last changed on 13 January 2026, which covers projects, recipes, connections, packages and API clients but not jobs or most other resources, and the Developer API MCP tool schemas weren't seen, so no contract for the API as a whole (0; the 5 carried from 1 October isn't a checklist value). llms.txt with Markdown twins of each page, re-read on 4 November (10). One reference page per resource stating each endpoint's purpose (12 of 20). Parameters typed and documented with enums, for example job status of succeeded, failed or pending (11 of 15). Request and response examples and a sample body for each documented error code (13 of 15). A dated changelog with entries every few weeks and dated deprecations, with no version in the API path; 12 isn't a checklist value and the nearest is the full 15. 0+10+12+11+13+15 = 61.

Agent ergonomics Windmill API + MCP +18

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

Workato API + MCP 55

AIRO MCP publishes seven tool categories and a docs_get tool that returns a live index, but no tool count. Developer API MCP tools are limited to what the client role allows, and tool-level RBAC for MCP servers went GA on 5 September 2026 (15 of 25). Offset pagination (offset_job_id, prev) and filters such as status and rerun_only (20; the 18 carried isn't a checklist value). Each response code has a documented error body, and messages say what was wrong and how many items were allowed ("Maximum 25 jobs can be repeated in a single request"), with err.item.not_found distinct from a permissions error (20; the 15 carried isn't a checklist value). No tool annotations or idempotency keys found (0). No official SDK; the Platform CLI is a Python command-line tool installed from its repository (0; the 3 carried isn't a checklist value). 15+20+20+0+0 = 55.

Security & auth Workato API + MCP +8

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

Workato API + MCP 68

API client bearer tokens limited by a client role (an endpoint list) and project scopes, legacy full-access keys removed on 14 October 2025, and OAuth 2.0 for AIRO MCP (30). Roles, tool-level RBAC and verified user access, which runs MCP tools with each end user's own app credentials. The AIRO MCP page, re-read on 4 November, says an API token connection runs with the workspace owner's identity and that the role's other privileges and project access settings don't limit it, so OAuth is the only least-privilege route to AIRO. No confirmation step before destructive tools found (13 of 20, from 16). Recipes return third-party data and no prompt-injection guidance was found (3 of 15). The activity audit log tags MCP actions "(via AIRO)" and job history is readable through the API (15). A responsible disclosure page (updated 14 January 2026) with a reporting form, which says Workato aims to acknowledge reports promptly but states no time. No security.txt (404 on 4 November), no bounty, and certifications unconfirmed because the trust centre needs JavaScript (7, the settled value for a disclosure policy with a reporting route and no acknowledgement time). 30+13+3+15+7 = 68.

Payments & pricing Windmill API + MCP +8

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.

Workato API + MCP 45

No x402, MPP or L402 (0). Workato Pro credit bundles are public, $75 for 2,500 credits a month up to $1,275 for 50,000, re-read on 4 November. The usage-metrics page names what each capability counts (tasks per action step, API calls, MCP proxy calls) but no credit rate per unit was found, and Enterprise is quoted, so plan-only public pricing (10; the 15 carried isn't a checklist value). Workato Free is a one-time 50,000-credit grant with no card (20). A person signs up in the browser and creates an API client (0). 0+10+20+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Score by category

CategoryWeightWindmill API + MCPWorkato API + MCPEdge
Reliability16%1565Workato API + MCP +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7961Windmill API + MCP +18
Agent ergonomics13%7355Windmill API + MCP +18
Security & auth14%6068Workato API + MCP +8
Payments & pricing10%5345Windmill API + MCP +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8760Windmill API + MCP +27
Transparency & trust7%7570Windmill API + MCP +5
Negative events≤15-11-3
TotalD 48/100C 57.8/100

Facts side by side

FactWindmill API + MCPWorkato API + MCP
KindHTTP APIHTTP API
VendorWindmill LabsWorkato
Hosted endpointhttps://app.windmill.dev/apihttps://www.workato.com/api
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceAGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only partsproprietary
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-032026-11-03
Terms last updatednot read yet2026-02-24
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularity18k stars, 126k npm/wk, 218k PyPI/wknone
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Workato API + MCP higher.

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

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.

Workato API + MCP

Developer API tokens are scoped by client role and project, and quotas are published per resource. No 429 or retry guidance was found, the only OpenAPI file covers 38 operations in the Platform CLI repository, and an AIRO MCP connection made with an API token runs with the workspace owner's permissions whatever its role.

Before you call either

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

Workato API + MCP

  1. Use the base URL for the workspace's data centre, and app.trial.workato.com for Free or Pro
  2. Give the agent an API client whose role lists only the endpoints it needs. The Developer API MCP server exposes those as tools
  3. Connect AIRO MCP with OAuth 2.0 rather than an API token, since a token runs with the workspace owner's permissions
  4. Repeat or cancel at most 25 jobs per call and no more than one call a second; back off on errors, since no retry guidance is published
  5. Every action step in a recipe is a task, so collapse loops before running at volume

Questions

Which is better for AI agents, Windmill API + MCP or Workato API + MCP?

Workato API + MCP scores 57.8 (C) on agent readiness against Windmill API + MCP's 48 (D), and leads in 2 of 7 scored categories. Windmill API + MCP leads on schema & documentation, agent ergonomics, payments & pricing, maintenance & community and transparency & trust.

Do Windmill API + MCP and Workato API + MCP need an API key?

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

Can an agent call Windmill API + MCP and Workato API + MCP without installing anything?

Yes. Windmill API + MCP has a hosted endpoint at https://app.windmill.dev/api and Workato API + MCP at https://www.workato.com/api.

Are Windmill API + MCP and Workato API + MCP open source?

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

Other comparisons with Windmill API + MCP or Workato 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.