Skip to main content
Notion’s remote MCP server connects with a single OAuth approval. It authenticates with standard OAuth 2.1 and dynamic client registration, so you paste the remote URL, click Continue, and approve a consent screen — you bring no client ID, secret, or token. The server exposes your Notion workspace, scoped to your own permissions.
This guide is a convenience based on Notion’s setup at the time of writing. Notion’s own MCP documentation is authoritative and may be more current. The requirements below come from Notion, not from MCP Manager. If a step here has drifted or a connection problem is specific to how Notion works, Notion support is the fastest path to an answer.

​
Before you start

  • A Notion account with access to the workspace your team’s AI tools will need to reach. The connection is per-user — each person authenticates with their own account and the server can only reach what they can already access.
  • A Notion login you can complete in a browser — the approval is an interactive, browser-based OAuth 2.1 flow.

​
Connect the server

1

Open the Servers page and add a server

On the Servers page, add a server to begin a new connection.
2

Paste the remote MCP URL and click Continue

Paste Notion’s remote MCP server URL, then click Continue to trigger discovery:
Notion MCP URL
https://mcp.notion.com/mcp
3

Approve Notion's consent screen

Detection resolves to Standard OAuth (dynamic client registration), so MCP Manager redirects you to Notion’s browser-based OAuth 2.1 flow. Sign in if prompted, then approve the consent screen. You provide no keys at this step. MCP Manager stores the resulting OAuth token encrypted and attaches it to every request it makes to Notion. The server’s tools are now available to add to a gateway.

​
Gotchas & things to keep in mind

  • Enterprise admin approval may be required. In Notion Enterprise workspaces with governance controls enabled, an admin must approve AI apps and MCP clients before they can connect. If your connection is blocked, check with your Notion workspace admin.
  • Access is per-user and permission-bound. Each person authenticates with their own Notion account, and the server can only reach what that account already can. Granting the connection never widens anyone’s Notion permissions.
  • Some tools require Business or Enterprise + Notion AI. Database view querying requires a Business plan with Notion AI; data source querying requires Enterprise + Notion AI. The tools appear in the gateway but return errors on workspaces where the required plan isn’t active.
  • Initial setup requires a human in the loop. The OAuth consent screen requires browser-based approval — fully automated provisioning without a human completing the flow is not supported. After the initial approval, MCP Manager holds and renews the token automatically, so agents can run unattended once the connection is established.
  • Per-user OAuth means per-user identity. Because each user approves their own consent, every action is attributable to that individual. See per-user versus shared identity for how this maps to gateway identities.

​
Further reading

Find & Connect MCP Servers

How MCP Manager detects authentication type, and how to find other servers’ URLs.

How MCP Manager authenticates

The OAuth flow Notion uses, in depth, plus per-user versus shared identity.

Identities for remote servers

How the OAuth credential you just approved is secured and made available.

Connect your AI client

Point Claude, Cursor, or another client at the gateway once the server is connected.

​
External sources

Get started with MCP

Notion’s authoritative guide to connecting via MCP — the URL, supported tools, and OAuth requirements.

MCP supported tools

The full list of tools Notion’s MCP server exposes and which plan tiers each requires.