Cédric Rittié

Notion
MCP · Knowledge

Notion

Notion's official MCP does semantic search across your workspace. Faster than native search, and Claude can cite and summarize several pages at once.

Use cases

  • Find a decision buried in a 40-page doc
  • Audit consistency of product docs
  • Generate a FAQ from tickets

Installation

1.Go to Notion → Settings → Connections → Notion MCP. Copy the integration URL generated for your workspace. This is a remote MCP, no local binary needed.

2.One line, one terminal
$ claude mcp add notion https://mcp.notion.com/mcp

Need to install Claude Code first? See the Claude Code page · Official docs

Concrete examples

"Trouve tous les docs où on parle de 'pricing v3' dans le workspace, classe par date récente."

Semantic search across the full workspace. Returns pages with a snippet of the relevant passage.

Sample output
→ Searching Notion workspace for "pricing v3"... 14 pages found

Top 5 by recent date
1. [Apr 12] Strategy/Pricing v3 — PRD draft
   Passage: "V3 introduces a Team tier at $99/mo with up to 5 seats..."

2. [Apr 8] Meetings/Q2 planning
   Passage: "Pricing v3 targeted for end-of-May release, pending..."

3. [Apr 3] Competitive/Notion vs Linear
   Passage: "Their pricing v3 might force us to rethink our Free tier..."

4. [Mar 28] Strategy/Pricing v3 — user research
   Passage: "Across 12 interviews, 8 users mentioned price as a blocker..."

5. [Mar 15] Meetings/Exec sync
   Passage: "Decision: we're starting work on pricing v3..."

The 9 other pages are older. Want me to summarize any of them?
"Résume le PRD 'Pricing v3' et extrais les 3 décisions clés, les 2 risques, les questions encore ouvertes."

Long doc read + info structuring. Useful to brief a colleague who hasn't read the PRD.

Sample output
→ Reading Pricing v3 — PRD draft (4,200 words)

Key decisions
1. Team tier at $99/mo, 5 seats included, +$15 per additional seat
2. 12-month grandfathering for existing Pro customers (no Q2 impact)
3. End-of-May release, announcement 2 weeks prior (mid-May)

Risks
1. Possible drop in Pro tier conversion (no A/B test, estimated
   -5 to -15% per the revenue team)
2. Billing complexity for mid-cycle upgrades (2-3 weeks dev estimated,
   no documented plan B)

Open questions
- What about current users with 10+ seats on Pro?
- What's the enterprise pricing (> 50 seats)?
- Should /pricing show all 3 tiers or 2 + "Contact us"?