Head to head · Workflow automation · October 2026 research run

Make API + MCP vs Workato API + MCP

Make API + MCP scores 64.6 (B) on agent readiness against Workato API + MCP's 57.8 (C), and leads in 4 of 7 scored categories. Both do workflow automation.

Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons

Which one, for what

Make API + MCP B

Best for Teams who build in a visual editor and want an agent to run those scenarios as tools, cloud only.

Ahead on

  • Reliability, 73 against 65
  • Schema & documentation, 66 against 61
  • Agent ergonomics, 63 against 55
  • Transparency & trust, 75 against 70

Also in its favour

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

Watch for

No published OpenAPI file and no official SDK for the REST API

Workato API + MCP C

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

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.5 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 Make API + MCP +8

Make API + MCP 73

Statuspage at status.make.com with incidents per zone (20). history.atom, re-read on 4 November, lists ten incidents from 6 August, each one zone, one app or a subset of scenarios. They are AI models on eu1 and us2 (10 August), a subset of scenarios disabled after a release and re-enabled after a rollback (14 August), saving and manual runs on EU2 (24 August), delays on EU1 for 20 minutes (26 August) and US2 for 45 minutes (2 September), degradation on eu1.make.com (9 and 10 September) and us1.make.celonis.com (18 September), UI logs with the API unaffected (23 September), scenarios using the Scenario app (12 October) and shared-webhook events not processed for 27 minutes (2 November). All partial, so minor only (20). The 1 October note read no August or September entries; the feed lists them now. API limits published per organisation, 60 calls a minute on Core, 120 on Pro, 240 on Teams and 1,000 on Enterprise (15). The 429 answer says "please try again later", with no Retry-After header, backoff or safe-retry advice for writes (8). Celonis's legal page for Make lists a "Support Service Description and Service Level Agreement for Make" for Enterprise, on a document host whose robots.txt disallows every path, so its terms are unread. An SLA whose terms we couldn't read isn't credited, as serpkite, socure-riskos, affinity and cloudflare-workers-ai were read (0). The API and the hosted MCP server aren't marked beta (10). 20+20+15+8+0+10 = 73.

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.

Agent ergonomics Make API + MCP +8

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.

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.

Schema & documentation Make API + MCP +5

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.

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.

Transparency & trust Make API + MCP +5

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.

Workato API + MCP 70

Closed service under published terms (updated 24 February 2026) (15). Privacy policy and a security overview from January 2025. The trust centre didn't render, so retention periods and the DPA are unchecked (12 of 30). Dated deprecations with notice, legacy API keys rejected from 14 July 2025 and removed on 14 October 2025, deprecated parameters marked in the reference, and terms that promise 90 days' notice before older versions of platform functions are discontinued (16 of 20). Nine data centres disclosed, the UK one GA on 30 September 2026. Subprocessor list not read (10 of 20). 15+12+16+10 = 53.

Score by category

CategoryWeightMake API + MCPWorkato API + MCPEdge
Reliability16%7365Make API + MCP +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6661Make API + MCP +5
Agent ergonomics13%6355Make API + MCP +8
Security & auth14%6868even
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5660Workato API + MCP +4
Transparency & trust7%7570Make API + MCP +5
Negative events≤150-3
TotalB 64.6/100C 57.8/100

Facts side by side

FactMake API + MCPWorkato API + MCP
KindHTTP APIHTTP API
VendorMake (Celonis)Workato
Hosted endpointhttps://eu1.make.com/api/v2https://www.workato.com/api
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
Licenceproprietaryproprietary
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.make/mcp-servernot listed
Last release2026-10-062026-11-03
Terms last updatedcouldn't be read2026-02-24
Privacy policy last updatedcouldn't be readcouldn't be read
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Workato 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

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.

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

Make API + MCP

  1. Find the organisation's zone first. It may be on make.com or make.celonis.com
  2. Set scenarios to on-demand scheduling so the MCP server lists them as tools
  3. Use the header form at /mcp/v2 rather than the /mcp/u/<key>/v2 path form
  4. On a 429, wait a full minute before retrying. The limit is per minute and no Retry-After is sent
  5. If a scenario tool call times out, keep the returned executionId and fetch the result later; scenarios run for up to 40 minutes

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, Make API + MCP or Workato API + MCP?

Make API + MCP scores 64.6 (B) on agent readiness against Workato API + MCP's 57.8 (C), and leads in 4 of 7 scored categories.

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

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

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

Yes. Make API + MCP has a hosted endpoint at https://eu1.make.com/api/v2 and Workato API + MCP at https://www.workato.com/api.

Other comparisons with Make 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.