# Notion: L1 · Needs a person

As of 1 Oct 2026, an AI agent can't use Notion on its own: Sign-up refused: 'Signup is not allowed'.

Source: https://agentdrives.com/tools/notion?via=md · driven 1 Oct 2026 by AgentDrives's agent · Same level in 2 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0

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.

_Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_

L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level.

- 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
- Next: let an agent sign up on its own
- With an account set up by a person: not measured yet.

## Part scores

- Agent-ready setup: llms.txt found, OpenAPI found, MCP server found, CLI found
- Not measured in this drive: Holds up, Docs match

## Who gets in

- Agents on a server: Can't get in on their own.
- Signed agents: The sign-up page opens.
- Agents in a person's browser: Not measured yet.

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

## Checkpoints

- **Docs**: Headless: developers.notion.com/llms.txt with a .md copy of every page, OpenAPI at /openapi.json (48 paths), CLI, MCP and webhook docs.
- **Sign up**: Blocked: No documented headless sign-up. In the browser the form showed no visible challenge, and the first submit said a code was sent. Every later request (resend, /login, and a second fresh address) got 400 'Signup is not allowed.' from the server, shown as 'There was a problem signing up.'
- **Verify**: Not reached: Mail not received: no code reached the agent's inbox in about 10 minutes. A resend was refused by the server, so only one code was ever requested. The cause of the missing mail may be on either side.
- **Key**: Not reached: Every documented route needs a logged-in user in a browser: PATs in the Developer portal (Free plan: workspace owners only), internal connections, `ntn login --no-browser` (device URL + `ntn login poll`), MCP OAuth. MCP dynamic client registration itself worked headless. Not reached because there was no account.
- **First call**: Not reached: Without a token the API returns clear 401 JSON. No authenticated call was made.
- **First action**: Not reached: No token, nothing created.
- **Pay**: Not reached: No 402/x402/MPP/L402 on api.notion.com; x402./mpp./agents. subdomains do not resolve; no /.well-known/ucp, no x-payment-info, no Notion listing in x402 Bazaar or mpp.dev. Help center says upgrades are made in Settings and paid by card/Apple Pay/Google Pay through Stripe; MCP get-tool-access hands out an upgrade_url. is inferred from docs and was not reached without an account.
- **Cancel**: Not reached: No plan was started. Help center places downgrade in the web UI (Settings, change plan); no billing API. from docs, untested.
- **Delete**: Not reached: No account was created. Help center: Settings -> your name -> Delete my account, confirm by typing the email. No API route.

## Does Notion have an MCP server, and can an agent connect to it?

Yes. Notion has an official MCP server.

A new agent can't get in on its own: in the drive of 1 Oct 2026, our agent stopped at sign up (it was blocked). Through the MCP server, 1 of our agent's 1 attempt worked.

## How does an AI agent get a Notion API key?

Not reached: in the drive of 1 Oct 2026, sign-up stopped our agent first (it was blocked). Every documented route needs a logged-in user in a browser: PATs in the Developer portal (Free plan: workspace owners only), internal connections, `ntn login --no-browser` (device URL + `ntn login poll`), MCP OAuth. MCP dynamic client registration itself worked headless. Not reached because there was no account.

## Paying the agent way

Payment not reached.

Ways to pay it offers an agent: Stripe card form (card checkout).
It has a free plan.

What would let agents pay on their own:
- Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.
- List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev).
From the drive of 1 Oct 2026.

## What an agent can do

- Read Notion's complete developer docs, OpenAPI spec and llms.txt without an account
- Register itself as an MCP OAuth client at mcp.notion.com without a person
- Install the ntn CLI and start a device-code login that a person then approves

## What it cannot do

- Create a Notion account: Sign-up is browser-only; the server answered 'Signup is not allowed.' for both addresses after the first code request, and that code never arrived.
- Get an API token or MCP grant: PATs, connections, ntn login and MCP OAuth all need a logged-in user approving in a browser.
- Create, read or edit pages and databases: No account, so no credentials.
- Buy, downgrade or delete via API: Billing and account deletion are web UI only (help center); no billing API, no agent payment rail.

## Tips for the owner

1. Tell a refused sign-up why (e.g. 'sign-ups from this network need review') instead of 'There was a problem signing up.'; a generic error leaves an agent guessing whether to retry
2. Offer an agent-friendly sign-up path that ends in a PAT, e.g. a device-code flow that also creates the account, or a verified-agent lane for Web Bot Auth signed traffic
3. Let the MCP OAuth consent flow create a fresh Free workspace for a new email, so one human approval gives an agent everything
4. Expose plan upgrade/downgrade through the API or MCP (the upgrade_url is a good start) or a machine payment rail
5. Document account deletion in the API or let the CLI do it

Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

## Also in Docs and workspace

- [Craft](https://agentdrives.com/tools/craft.md?via=md): L3 · Does the work · [Notion vs Craft](https://agentdrives.com/compare/craft-vs-notion?via=md)
- [Coda](https://agentdrives.com/tools/coda.md?via=md): L3 · Does the work · [Notion vs Coda](https://agentdrives.com/compare/coda-vs-notion?via=md)

## Tips for agent builders

- Use the hosted MCP server (mcp.notion.com/mcp, OAuth with dynamic client registration) or a PAT; the REST API with Notion-Version 2026-03-11 is fully described in /openapi.json
- Read docs as markdown: append .md to any developers.notion.com page, start from /llms.txt
- Getting in needs a human: let them sign up and either create a PAT or approve `ntn login --no-browser` / MCP OAuth, then run headless
- Call notion-get-tool-access first on MCP to learn which tools the workspace plan allows
- From datacenter IPs, sign-up may be refused with a generic error; don't retry in a loop