DEV Community

Cover image for Notion MCP for Claude Code: The Official Hosted Server in 1 Command, No API Token
quickpromptco
quickpromptco

Posted on Edited on Originally published at quickpromptco.com

Notion MCP for Claude Code: The Official Hosted Server in 1 Command, No API Token

Your specs, meeting notes, and bug tickets live in Notion. Your code lives in Claude Code. So every task starts with the same ritual: open the Notion page, copy the requirements, paste them into the terminal, and hope you didn’t miss the comment thread at the bottom where the scope changed.

Notion MCP is Notion’s official hosted MCP server at mcp.notion.com . Claude Code signs in with your Notion account through OAuth and can then search your workspace, read pages and databases as Markdown, and create or update pages, all limited to what you can already see. There’s no API token, no JSON config, and nothing to run locally.

What the full guide covers:

  • What You’ll Need
  • Step-by-Step Setup
  • What Each Piece Does
  • Verify It’s Actually Working

The commands, our own test notes, and the troubleshooting steps are in the full guide, which we keep up to date:

Read the full guide on quickpromptco.com

Top comments (1)

Collapse
 
koda2026 profile image
Harun - solo dev •

quickpromptco, this is a highly practical and timely guide. the shift from self-hosted api tokens to an oauth-backed hosted mcp server is a massive win for security posture. it enforces least privilege and completely eliminates the risk of leaking ntn_ tokens in .env files or dotfiles.

your warning about prompt injection via notional page content is the most critical takeaway here. when an llm can read arbitrary user-generated content and then execute write tools based on it, that content becomes an active attack vector. keeping execution approval prompts enabled for write tools is an absolute must.

additionally, the --scope project approach for committing .mcp.json is brilliant for team reproducibility. it standardizes the tooling surface across the repo while forcing each developer to authenticate with their own credentials, keeping the permission boundary perfectly clean.

fantastic, no-fluff breakdown of the modern mcp workflow. 🐯🔗