4 minTime to key
NoNo-human path
1Human gates
9/10Onboarding score
Email verification
Fastest path to a key
- Sign up at notion.so with Google/Apple OAuth (or email + 6-digit login code)
- Onboarding creates a personal workspace
- Agent installs CLI: curl -fsSL https://ntn.dev | bash; run 'ntn login' (browser authorize) -> CLI can make API calls ('ntn api v1/users')
- Alternative raw token: Developer portal https://www.notion.so/developers/tokens > create Personal Access Token (name, workspace, capabilities: Notion API / Workers)
- Call GET https://api.notion.com/v1/users/me with Bearer PAT + Notion-Version: 2026-03-11
- Working API key
Biggest gap
Remote MCP is OAuth-only (no PAT bearer documented) and still labelled Beta in its resource metadata; local server abandoned.
Worth copying
Every .md doc page begins with a pointer telling agents to fetch llms.txt first, and PATs eliminated the old 'share every page with your integration' trap.
Sources (8) · checked 2026-10-11
- https://developers.notion.com/llms.txt
- https://developers.notion.com/docs/mcp
- https://developers.notion.com/guides/get-started/personal-access-tokens.md
- https://developers.notion.com/cli/get-started/overview.md
- https://developers.notion.com/guides/mcp/get-started-with-mcp.md
- https://developers.notion.com/guides/mcp/build-mcp-client.md
- https://developers.notion.com/guides/mcp/hosting-open-source-mcp.md
- https://mcp.notion.com/.well-known/oauth-authorization-server
69Readiness score / 100
L3 Agent-operableBeats 89% of 1,846 companies
Access20/20
Context17/20
Interfaces20/32
Onboarding8/19
Trust4/9
llms.txt · root
MCP · https://developers.notion.com/mcp
OpenAPI · https://developers.notion.com/openapi.json
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +6 Agents can self-register OAuth clients. Support dynamic client registration (RFC 7591) or client ID metadata documents so MCP clients connect in one click.
- +5 OAuth discovery metadata. Publish RFC 8414 authorization-server and RFC 9728 protected-resource metadata.
All 20 checks
- PASSAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- PASSContent is server-rendered4
- PASSllms.txt exists8
- FAILllms-full.txt exists3
- PASSDocs available as markdown6
- PASSSitemap2
- PASSStructured metadata1
- PASSPublic developer docs4
- PASSMachine-readable API spec8
- FAILRemote MCP server for the product12
- PASSDocs MCP or searchable docs4
- PASSSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- PASSSelf-serve API keys5
- PASSFree tier or test mode3
- PASSAgent manifests4
- FAILsecurity.txt2
- FAILPublic status page3
Your fix pack: 7 changes, up to +31 points
Each change is ready to paste, filled in for notion.so, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/notion.so)