Head to head · Workflow automation · October 2026 research run

n8n API + MCP vs Workato API + MCP

Workato API + MCP scores 57.8 (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, 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

n8n API + MCP D

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 61
  • Agent ergonomics, 79 against 55
  • Maintenance & community, 80 against 60
  • Transparency & trust, 87 against 70

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

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 20

Also in its favour

  • A hosted endpoint, with nothing to install
  • 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 Workato API + MCP +45

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.

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.

Schema & documentation n8n API + MCP +31

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.

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 n8n API + MCP +24

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.

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.

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.

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.

Transparency & trust n8n API + MCP +17

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.

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

CategoryWeightn8n API + MCPWorkato API + MCPEdge
Reliability16%2065Workato API + MCP +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9261n8n API + MCP +31
Agent ergonomics13%7955n8n API + MCP +24
Security & auth14%7068n8n API + MCP +2
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8060n8n API + MCP +20
Transparency & trust7%8770n8n API + MCP +17
Negative events≤15-15-3
TotalD 49.3/100C 57.8/100

Facts side by side

Factn8n API + MCPWorkato API + MCP
KindHTTP APIHTTP API
Vendorn8nWorkato
Hosted endpointno (local only)https://www.workato.com/api
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceSustainable Use License (fair-code, source-available)proprietary
Tools exposed57none
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-042026-11-03
Terms last updatedcouldn't be read2026-02-24
Privacy policy last updated2026-09-28couldn'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
Popularity206k stars, 113k npm/wknone
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate 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

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.

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

n8n API + MCP

  1. 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
  2. Ask for only the OAuth scopes the job needs. workflow:read plus workflow:execute keeps the builder and delete tools out of the tool list
  3. Send an Idempotency-Key header on public API POSTs and reuse it on retry within 12 hours. A 409 means the first request is still running
  4. Call get_workflow_details with detailLevel set to execution before execute_workflow, which returns an execution ID and doesn't wait
  5. On Cloud trial accounts /api/v1 won't answer. Use the MCP server or a paid plan

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

Workato API + MCP scores 57.8 (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, maintenance & community and transparency & trust.

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

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

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

No hosted endpoint is listed for n8n API + MCP. Workato API + MCP has a hosted endpoint at https://www.workato.com/api.

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