Notion MCP · Connects via OAuth from your own MCP client · Powered by mcpcio.com

About This Demo

Info Only

Notion MCP uses per-user OAuth authentication. That's the right design for a productivity tool — and it's why this page can't show you a live demo the way our Shopify or GitHub pages do.

Why No Live Demo

Notion MCP requires per-user authentication, not a shared API key

Notion's hosted MCP server at https://mcp.notion.com/mcp uses OAuth 2.0 — each user completes a browser-based authorization flow with their own workspace, and the resulting access token is tied to that specific user. Per Notion's own documentation, the hosted MCP "does not support bearer token authentication" — there's no way for a shared server like ours to authenticate on behalf of anonymous visitors.

This is the right design for a productivity tool. Every person using Notion MCP should act against their workspace with their permissions. A shared public demo would have to either expose one real workspace to every visitor on the internet, or silently simulate responses while claiming to be live. Neither is a demo worth shipping from a site about being honest about MCP.

We'll build a live demo here the moment Notion adds a headless authentication path. Until then, the fastest way to see Notion MCP in action is to connect it to your own workspace — which takes about two minutes.

Try it yourself in about 2 minutes
  1. Open Claude Desktop → Settings → Connectors → Add Custom Connector
  2. Paste the server URL: https://mcp.notion.com/mcp
  3. Complete the OAuth flow in your browser — choose which pages the connection can see
  4. Ask Claude: "what are my current projects in Notion?"

Not a Claude user? Notion MCP works with any MCP-compatible client.

Cursor — Add "notion": {"url": "https://mcp.notion.com/mcp"} to your ~/.cursor/mcp.json and complete OAuth when you first call a Notion tool.

ChatGPT Pro — Notion is listed as a built-in connector. Settings → Connected Apps → Notion.

Other MCP clients — Any client that supports remote MCP servers with OAuth can connect. See Notion's client integration guide.

Could you use a stored OAuth token on the server instead?

Technically, yes — an operator could complete OAuth once with a personal account, store the resulting token as a server secret, and proxy every visitor's request through that single token. We considered it.

We decided against it for three reasons: (1) every demo visitor would then be reading and potentially writing against one real person's workspace, (2) Notion's own security guidance treats shared-token patterns as unintended use, and (3) the site's thesis is showing MCPs the way real clients use them — and real clients don't share one OAuth token across thousands of users. An honest "no live demo" is better than a live demo that misrepresents how the tool actually works.

If Notion ships bearer-token support for the hosted MCP in the future, we'll replace this page with a real live demo immediately.