Notion MCP Setup for Cursor
Version: 1.0
Date: February 2026
1. Purpose
This guide enables Cursor AI agents to read and write to your Notion workspace (pages, databases, blocks) via Notion’s hosted MCP. Authentication is per user: each person signs in to their own Notion account when they first use the integration.
2. Installation & Configuration
Already configured in brainforge-platform
The brainforge-platform repo includes .cursor/mcp.json with the Notion MCP. When you open this repo as your Cursor workspace, the MCP is loaded automatically.
Location: .cursor/mcp.json (at repo root)
"notion": {
"url": "https://mcp.notion.com/mcp"
}Do not add any NOTION_API_KEY, token, or auth headers to this config. Per-user auth is handled by OAuth; secrets stay on your machine.
Per-user OAuth (automatic)
- After opening the repo in Cursor, use a Notion-related action (e.g. “search my Notion” or any Notion MCP tool).
- Cursor will prompt you to complete the OAuth flow (redirect to Notion → sign in → authorize).
- Your connection is stored locally in Cursor (per user, per machine). Other repo users get their own prompt and their own connection.
No shared tokens, no secrets in the repo.
3. Troubleshooting
- First time: If the OAuth flow doesn’t start, try Developer: Reload Window and use a Notion tool again.
- Wrong workspace: Disconnect in Cursor (MCP settings) and reconnect to choose a different Notion workspace.
- Permissions: You only see and edit Notion content you have access to in the workspace you connected.
4. Reference
- Notion MCP URL:
https://mcp.notion.com/mcp - Official docs: Notion MCP – Get started
- Config location:
.cursor/mcp.json(repo root)