A well-documented, agent-first community Notion MCP server. Its two-tool surface with on-demand schemas, batching, idempotency, retries, access controls, and HTTP transport make it a strong fit for unattended and token-sensitive deployments. Caveats: it is not official Notion software, so trust requires auditing or self-hosting, and the HTTP mode must be secured with an auth token.
A third-party (awkoy) Notion Model Context Protocol server — not maintained by Notion. It authenticates with a token (Personal Access Token or Internal Integration secret), so it runs headless in CI, cron jobs, background agents, and self-hosted deployments where OAuth-only hosted MCP cannot. The server exposes exactly two MCP tools (notion_execute and notion_describe) that dispatch 43 operations across pages, blocks, databases, data sources, views, comments, users, and files, with operation schemas loaded on demand to keep the connection footprint small. It adds batched mutations with atomic rollback, idempotency keys, automatic rate-limit retry, full markdown round-trip, Notion templates, file uploads, flattened query rows, and access control via NOTION_READ_ONLY and operation allow/block lists. Beyond stdio it supports a Streamable HTTP transport (single-tenant, protectable with MCP_AUTH_TOKEN).
claude mcp add notion -s user -e NOTION_TOKEN=ntn_… -- npx -y notion-mcp-server; for Claude Desktop / Cursor add {"command":"npx","args":["-y","notion-mcp-server"],"env":{"NOTION_TOKEN":"…"}} to mcpServers config; 3. Claude Desktop alternatively supports a one-click .mcpb extension download; 4. Docker: docker run --rm -i -e NOTION_TOKEN ghcr.io/awkoy/notion-mcp-server:latest (-i required for stdio); 5. Remote mode: start with MCP_TRANSPORT=http and always set MCP_AUTH_TOKEN when binding a non-loopback host.{"mcpServers":{"notion":{"command":"npx","args":["-y","notion-mcp-server"],"env":{"NOTION_TOKEN":"ntn_paste_your_token_here"}}}}