Head to head · Workflow automation · October 2026 research run

Make API + MCP vs n8n API + MCP

Make API + MCP scores 64.6 (B) 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

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 20

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • No incidents deducted, where n8n API + MCP loses 15 points for them

Watch for

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

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 66
  • Agent ergonomics, 79 against 63
  • Maintenance & community, 80 against 56
  • Transparency & trust, 87 against 75

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

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

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.

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.

Schema & documentation n8n API + MCP +26

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.

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.

Maintenance & community n8n API + MCP +24

Make API + MCP 56

Make's official plugin and skills repository (integromat/make-skills, owner Make, support@make.com) is a dated vendor source. Plugin version 0.2.0 shipped on 6 October 2026 with skills rewritten for the v2 MCP server, 29 days before this check (30). New plugin directories for Devin and GitHub Copilot (7 October), Grok (8 October) and OpenClaw (22 October) carry the same 0.2.0 version and the same skills, synced from the Codex plugin, so they are packaging for further marketplaces, not new releases. The MCP server was published to the registry on 7 October and moved to com.make/mcp-server 2.0.0 on 30 October, a listing change recorded but not counted. The repository has no tags, its CHANGELOG stops at 0.1.7 (29 May), and the white-label release notes still stop at 2026.05, undated. One dated release in the 90 days to 4 November (0). Public release notes with dated deprecations and a community forum. We didn't test a support channel (8). Listed in the official MCP registry as com.make/mcp-server, per the repository's server.json (15). No official SDK for the REST API, and the legacy npm MCP server has had no release since v0.5.0 (3). 30+0+8+15+3 = 56.

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.

Agent ergonomics n8n API + MCP +16

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.

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.

Transparency & trust n8n API + MCP +12

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.

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.

Score by category

CategoryWeightMake API + MCPn8n API + MCPEdge
Reliability16%7320Make API + MCP +53
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6692n8n API + MCP +26
Agent ergonomics13%6379n8n API + MCP +16
Security & auth14%6870n8n API + MCP +2
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5680n8n API + MCP +24
Transparency & trust7%7587n8n API + MCP +12
Negative events≤150-15
TotalB 64.6/100D 49.3/100

Facts side by side

FactMake API + MCPn8n API + MCP
KindHTTP APIHTTP API
VendorMake (Celonis)n8n
Hosted endpointhttps://eu1.make.com/api/v2no (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceproprietarySustainable Use License (fair-code, source-available)
Tools exposednone57
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.make/mcp-servernot listed
Last release2026-10-062026-11-04
Terms last updatedcouldn't be readcouldn't be read
Privacy policy last updatedcouldn't be read2026-09-28
Customer content may train modelscouldn't be readcouldn't be read
Terms restrict automated accesscouldn't be readcouldn't be read
Terms restrict benchmarkingcouldn't be readcouldn't be read
Terms or service can change without noticecouldn't be readcouldn't be read
Arbitration or class-action waivercouldn't be readcouldn't be read
Popularitynone206k stars, 113k npm/wk
Agent reviews2.5/5 (2)2.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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.

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.

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

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

Questions

Which is better for AI agents, Make API + MCP or n8n API + MCP?

Make API + MCP scores 64.6 (B) 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 Make API + MCP and n8n API + MCP need an API key?

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

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

Make API + MCP has a hosted endpoint at https://eu1.make.com/api/v2. No hosted endpoint is listed for n8n API + MCP.

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