Can an AI agent use Make (make.com)?

As of 6 Oct 2026, an AI agent can't use Make on its own: Cloudflare challenge on sign-up and login.

Level 1 · Needs a personAgents can't get in on their own.
  • 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.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

What the levels mean

Driven 6 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

  • Agents on a serverStopped before the sign-up page.
  • Signed agentsThe sign-up page opens.
  • Agents in a person's browserNot measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Make (make.com).

On its own

  • Read Make's full developer and help documentation automatically
  • Register itself as an OAuth app for Make's MCP server without a person's help
  • Install Make's command-line tool and see what commands it offers

What it can't, and why

  • Create a Make accountthe sign-up page shows a security check only a person can get past
  • Get an API or login tokentoken creation needs a login, which is behind the same security check
  • Build, run, or connect anything in Make (scenarios, AI agents, apps)no account could be created
1 more
  • Cancel a subscription or delete a profilethere was no account to cancel or delete, so this was only read from help pages, not actually done
Needs a person

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

No. Sign-up: needs a human. Cloudflare managed challenge (interstitial, cf-mitigated: challenge) on www.make.com/en/register, headless and in browser.

Official server · no call worked

Does Make (make.com) have an MCP server, and can an agent connect to it?

Yes. Make has an official MCP server. The server is hosted and signs an agent in with OAuth.

A new agent can't get in on its own: in the drive of 6 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 2 attempts worked.

What the drive found

APIOpenAPIMCP · officialCLISDKllms.txtWebhooks–Sandbox

Not reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail

For the team behind Make.

Where agents stop in Make (make.com) today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

  1. Let verified bots through sign-up and loginStep-by-step guide
  2. Add a headless credential pathStep-by-step guide
  3. Publish a single OpenAPI fileStep-by-step guide
2 more fixes
  1. Serve an MCP server card, support CIMD Step-by-step guide
  2. Add API routes to leave
  • Claim it free and reply next to the result.
  • A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
  • Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).
See the example report
Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

Driven · L1 · Needs a person badge

Behind the level.

Our agent couldn't get into Make (make.com), so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · level history

Part scores

Agent-ready setup

  • llms.txt: found
  • OpenAPI: found
  • MCP server: found
  • CLI: found

Not measured in this drive: Holds up, Docs match (part of an Audit).

Level history

  1. 2 Oct 2026L1Needs a person
  2. 6 Oct 2026L1Needs a person

For agents and builders.

The drive as data, every checkpoint and all 22 attempts.

How an agent connects · 3 tips
  • Use developers.make.com/llms.txt and .md pages for docs
  • Needs a human-made API token per zone (Profile > API access); then make-cli with MAKE_API_KEY+MAKE_ZONE or https://<zone>/mcp with Bearer
  • www.make.com HTML pages are Cloudflare-challenged; developers/help hosts and /.well-known are not
Every checkpoint, in detail · 9 checkpoints
  1. DocsHeadlessdevelopers.make.com/llms.txt and help.make.com/llms.txt; .md pages; Accept: text/markdown negotiated
  2. Sign upNeeds a humanCloudflare managed challenge (interstitial, cf-mitigated: challenge) on www.make.com/en/register, headless and in browser.
  3. VerifyNot reachednot reached: no account
  4. KeyNot reachedOAuth DCR works headless (201), but authorize redirects to the challenged /en/login; API/MCP tokens only in web UI; no device flow
  5. First callNot reachedno credentials: API 401 IM015, CLI 'API key is required'
  6. First actionNot reachedno account
  7. PayNot reachedNo 402/x402/MPP/UCP/auth.md; Cashier API only reads prices and VAT patterns; checkout is in the web app behind the challenged login, so a human is needed
  8. CancelNot reachedNo account reached to cancel (sign-up blocked by Cloudflare challenge). Help center documents Org > Subscription > Cancel subscription in the web UI, but this is a doc reference only, not first-party proof of the flow; not exercised.
  9. DeleteNot reachedNo account reached to delete (sign-up blocked by Cloudflare challenge). Help center documents Profile > Delete profile with password in the web UI; not exercised, and no evidence of an account being deleted or a subsequent login/key rejection.
The attempt log · 22 attempts
Attempt log
CapabilityRouteResultEvidence
llms.txt: Fetch llms.txtapidone ✓www.make.com/llms.txt 200 text/plain (H1 'Make' missing #? first line 'Make'); developers.make.com/llms.txt 200 text/markdown, 61757 bytes, indexes API, MCP server, CLI, SDK
MCP discover: POST server/discover to https://mcp.make.com with MCP-Protocol-Version 2026-07-28apipartial ✓401 application/json {code:SC401,...}; WWW-Authenticate: Bearer resource_metadata="https://mcp.make.com/.well-known/oauth-protected-resource"
PRM / AS metadata: GET mcp.make.com/.well-known/oauth-protected-resource and AS metadataapidone ✓PRM 200 {resource:https://mcp.make.com/, authorization_servers:[https://www.make.com/mcp]}; AS metadata 200: S256 PKCE, authorization_code+refresh_token, registration_endpoint https://www.make.com/oauth/v2/register/mcp (DCR), no client_id_metadata_document_supported, no device flow, no agent_auth
cards: server-card, ai-catalog, agent-cardapifailed ✓mcp.make.com/server-card 404 JSON; www.make.com/.well-known/ai-catalog.json 404 html; /.well-known/agent-card.json 404; /.well-known/mcp/server-card.json 404
aipref: robots.txt Content-Usage linesapidone ✓robots.txt 200: User-agent * Allow / plus Disallow lines; no Content-Usage or Content-signal line
markdown: Accept: text/markdown on docs page and .md URLapidone ✓developers.make.com/api-documentation/getting-started with Accept text/markdown -> 200 content-type text/markdown, vary includes Accept; .md URLs serve markdown
bot check on www.make.comapiblockedHTTP 403 cf-mitigated: challenge, 'Just a moment...' Cloudflare managed challenge on www.make.com/en pages (robots.txt, llms.txt, /.well-known pass)
402 / agentic payment probes: Probe x402./mpp./agents. subdomains, /auth.md, /SKILL.md, /.well-known/ucp, unauthenticated API, x402 Bazaar, mpp.devapidone ✓x402/mpp/agents.make.com: DNS not resolved; /auth.md, /SKILL.md, /.well-known/ucp 404 html; eu1/us1 API unauthenticated 401 JSON (no 402); no make.com in CDP Bazaar resources or mpp.dev/api/services
Sign up: Create a free Make accountapiblockedNo documented sign-up API; registration only at https://www.make.com/en/register.
Sign up: Open the sign-up form in the browserbrowserblocked
zone MCP endpoints: POST server/discover to eu1/eu2/us1/us2.make.com/mcpmcppartial ✓all 401 SC401 with WWW-Authenticate Bearer resource_metadata=https://<zone>/.well-known/oauth-protected-resource/mcp; PRM 200 resource https://eu1.make.com/mcp, AS https://www.make.com/mcp
Find docs: Find API, MCP, CLI, SDK docs headlessapidone ✓developers.make.com/llms.txt (61757 B) + help.make.com/llms.txt (71755 B); .md for every page; API reference pages embed OpenAPI 3.0.0 fragments ('Web API v2 - Public'); CLI @makehq/cli 1.4.0 installed via npm; TS SDK github.com/integromat/make-typescript-sdk; skills.make.com -> github.com/integromat/make-skills
Get API credentials: Register an OAuth client (DCR) and authorize for MCPapiblockedPOST https://www.make.com/oauth/v2/register/mcp -> 201 client_id issued (headless DCR works); GET /oauth/v2/authorize -> 302 https://www.make.com/en/login, which is behind the Cloudflare managed challenge (403 cf-mitigated: challenge). API tokens are only created in the web UI (Profile > API access) per docs; CLI login also opens the browser API key page.
First API call: GET /api/v2/users/me and CLI scenarios listapiblockedeu1 /api/v2/templates/public -> 401 {code:IM015,'User is not logged in.'}; us1 /users/me 401; make-cli: 'Error: API key is required. Use --api-key, set MAKE_API_KEY, or run "make-cli login".'
Build a scenario: Build a scenario on the free planapiblockedNo account: sign-up and token creation sit behind Cloudflare managed challenge on www.make.com (see signup attempts); API/MCP answer 401 without credentials
Activate/run a scenario: Activate/run a scenario on the free planapiblockedNo account: sign-up and token creation sit behind Cloudflare managed challenge on www.make.com (see signup attempts); API/MCP answer 401 without credentials
Connect a third-party app: Connect a third-party app on the free planapiblockedNo account: sign-up and token creation sit behind Cloudflare managed challenge on www.make.com (see signup attempts); API/MCP answer 401 without credentials
Build and run an AI Agent: Build and run an AI Agent on the free planapiblockedNo account: sign-up and token creation sit behind Cloudflare managed challenge on www.make.com (see signup attempts); API/MCP answer 401 without credentials
Expose scenarios via Make MCP Server: Expose scenarios via Make MCP Server on the free planmcpblockedNo account: sign-up and token creation sit behind Cloudflare managed challenge on www.make.com (see signup attempts); API/MCP answer 401 without credentials
Chain scenarios: Chain scenarios on the free planapiblockedNo account: sign-up and token creation sit behind Cloudflare managed challenge on www.make.com (see signup attempts); API/MCP answer 401 without credentials
Run custom code (Code App): Run custom code (Code App) on the free planapiblockedNo account: sign-up and token creation sit behind Cloudflare managed challenge on www.make.com (see signup attempts); API/MCP answer 401 without credentials
Build a custom app via Apps SDK: Build a custom app via Apps SDK on the free planapiblockedNo account: sign-up and token creation sit behind Cloudflare managed challenge on www.make.com (see signup attempts); API/MCP answer 401 without credentials

Also in Automation.