Craft vs Notion for AI agents
As of 6 Oct 2026, Craft gets an AI agent further: L3 · Does the work against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Sign-up in a browser.
- Use: 78% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
In on its own; 78% of the work done. Next: do 80% of the core work (now 78%)
Gets in on its own and does the work: L3 · Does the work. Our agent passed every checkpoint it tried headless, with no step blocking it outright. Sign-up used an email-code web form behind an invisible challenge that let it through, and credentials needed one browser approval for MCP; from there it created a document through the API and read it back. Through the API it drove documents, folders, tasks, daily notes, collections and whiteboards, with publishing, sharing and the Assistant reachable only in the browser. Upgrading opens a hosted card form a human has to complete, and deleting the account is a browser-only step with no matching API route, though it fully revoked the agent's access afterward.
Gets furtherDriven 6 Oct 2026 · The drive and its evidence- 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: blocked. Next: let an agent sign up on its own
Needs a person to sign up first: L1 · Needs a person. Notion's form showed no challenge and said a code was sent, but no code reached our agent's inbox, and a resend got "Signup is not allowed." from the server; a second try from a fresh address got the same answer. The docs are strong regardless: an OpenAPI reference, a CLI and an official hosted MCP server with dynamic client registration, plus markdown pages for every doc. Without a token our agent made no call and did no work, so paying and deleting the account were never reached.
Driven 1 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
CraftIn on its own; 78% of the work done
NotionStopped at sign up: blocked
| Checkpoint | Craft | Notion |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Blocked |
| Verify | In a browser | Not reached |
| Key | In a browser | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | In a browser | Not reached |
| Cancel | Not needed | Not reached |
| Delete | In a browser | Not 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
| Craft | Notion | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 5 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 0 | 7 |
| Work done | 78% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Craft | Notion | |
|---|---|---|
| Bot check | reCAPTCHA (invisible) let it through at sign up | None met |
| Wall type | No bot-check wall | No bot-check wall |
| First wall | None | Sign-up refused: 'Signup is not allowed' |
| A person helped | No | No |
Level and part scores.
| Craft | Notion | |
|---|---|---|
| Level | L3 · Does the work | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 100 of 100, good |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.1.1 (1 version behind) | None recorded |
| Security | Reported privately to the owner | No review in this drive |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Craft | Notion | |
|---|---|---|
| Pay | Reaches the checkout | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not reached |
| Delete the account | In a browser | Not reached |
How each one takes payment
- Craft: Reaches the checkout: stopped at the card form.
- Notion: Payment not reached.
Craft vs Notion: the short answers.
Which can an AI agent use, Craft or Notion?
Craft gets an AI agent further: L3 · Does the work against L1 · Needs a person. With Craft our agent got in on its own and did 78% of the work; with Notion it was stopped at sign up (blocked). Driven 6 Oct 2026 (Craft) and 1 Oct 2026 (Notion).
Can an AI agent sign up for Craft and Notion on its own?
Craft: yes, in a browser. Notion: no, blocked.
Do Craft and Notion have an MCP server?
Craft: yes (official). Notion: yes (official).
Can an AI agent delete its Craft or Notion account?
Craft: yes, in a browser. Notion: 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.