Make vs n8n for AI agents

As of 12 Oct 2026, both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human).

MakeL1Needs a person
  • Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
  • Access: Can't sign up.
  • Use: Work not reached.
  • Pay: Payment not reached.
  • Leave: Leaving not reached.

Stopped at sign up: needs a human. Next: let an agent sign up on its own

L1 · Needs a person describes Make today: our agent could not get in on its own. It stopped at signup, where a Cloudflare managed challenge on the registration page did not clear, even for a signed, docs-reading agent. OAuth client registration worked on its own, but the authorize step redirects to that same challenged login, and API and MCP calls both failed for want of a key. Make's docs are agent-friendly: llms.txt, markdown pages, a full REST API, CLI, SDK and hosted MCP server, all unreachable without a person completing signup first. Checkout, subscription cancellation and profile deletion all sit behind that same human login and were never reached.

Driven 6 Oct 2026 · The drive and its evidence
n8nL1Needs a person
  • Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
  • Access: Can't sign up.
  • Use: Work not reached.
  • Pay: Payment not reached.
  • Leave: Leaving not reached.

Stopped at sign up: needs a human. Next: let an agent sign up on its own

A person has to open the account first: this is L1 · Needs a person. Our agent cleared email verification, but the final sign-up form carries a visible Cloudflare Turnstile box and refused submit until it was checked, so no instance was created. Past that step n8n hands off to an official MCP server, a public API and a CLI, with docs that already speak agent: llms.txt, Markdown pages and a docs MCP server. Those same docs say the API isn't available during the free trial. Both API keys and MCP tokens are made only in the web UI, so a person stays in the loop after signup too.

Driven 12 Oct 2026 · The drive and its evidence

The two summaries: written and checked by our agents from each product's drive. How we write.

Where each one stops.

MakeStopped at sign up: needs a human

n8nStopped at sign up: needs a human

Make and n8n, checkpoint by checkpoint
CheckpointMaken8n
DocsHeadlessHeadless
Sign upNeeds a humanNeeds a human
VerifyNot reachedIn a browser
KeyNot reachedNot reached
First callNot reachedNot reached
First actionNot reachedNot reached
PayNot reachedNot reached
CancelNot reachedNot reached
DeleteNot reachedNot reached

Headless or in a browser.

How our agent passed each checkpoint, and what each product offers an agent.

Checkpoints by route, API, MCP, CLI and SDK
Checkpoints by how our agent passed them, and what each product offers an agent
Maken8n
Headless (checkpoints)11
In a browser (checkpoints)01
Needs a human (checkpoints)11
Blocked (checkpoints)00
Not tested (checkpoints)76
Work doneNot measuredNot measured
APIYesYes
OpenAPIYesYes
MCP serverYes (official)Yes (official)
CLIYesYes
SDKYesNo
llms.txtYesYes

Bot checks, and where a person was needed.

Walls our agent met
Maken8n
Bot checkCloudflare managed challenge (interstitial) stopped it at sign up, with a visible challengeCloudflare Turnstile stopped it at sign up, with a visible challenge
Wall typeA check of our network and browserA check of our network and browser
First wallCloudflare challenge on sign-up and loginCloudflare Turnstile on the sign-up form
A person helpedNoNo

A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.

Level and part scores.

Make and n8n: level and part scores, 0 to 100
Maken8n
LevelL1 · Needs a personL1 · Needs a person
Agent-ready setup100 of 100, good100 of 100, good
StandardsMCP client registration (behind) · OpenAPI 3.0.0 (2 versions behind)None recorded

Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.

Pay, cancel and delete.

Paying, cancelling and deleting the account
Maken8n
PayPayment not reachedPayment not reached
Free plan or trialFree planTrial, no card
CancelNot reachedNot reached
Delete the accountNot reachedNot reached
How each one takes payment
  • Make: Payment not reached.
  • n8n: Payment not reached.

Make vs n8n: the short answers.

Which can an AI agent use, Make or n8n?

Both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human). Driven 6 Oct 2026 (Make) and 12 Oct 2026 (n8n).

Can an AI agent sign up for Make and n8n on its own?

Make: no, needs a human. n8n: no, needs a human.

Do Make and n8n have an MCP server?

Make: yes (official). n8n: yes (official).

Can an AI agent delete its Make or n8n account?

Make: not reached. n8n: not reached.

The drives and the category.

Put your own shortlist side by side.

A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.