BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

Notion MCP

Connector Communication Solid
Works inClaude Code Claude Cowork Claude Chat
Solid Tested by us

The only way to read and write Notion from Claude.

Official Notion MCP server (makenotion) — search, retrieve pages, query data sources, create/update pages, manage databases, add comments, and read/write page content as Markdown. This local server authenticates with a Notion internal-integration token; Notion's hosted remote MCP (mcp.notion.com) offers OAuth instead. Version 2.0 migrated to Notion API 2025-09-03 with data sources as the primary database abstraction (22 tools).

4,522 starsMIT (commercial OK)FreemiumNo code needed
Official tool maintained by Notion.

The only way to read and write Notion from Claude. Most useful for teams using Notion as their documentation hub — automates page creation, database queries, and content updates.

Teams using Notion for documentation, project tracking, or knowledge management. Works across Claude Code, Cowork, and Chat.

Claude Code Claude Cowork Claude Chat

https://github.com/makenotion/notion-mcp-server

By Notion

How to Get It

Option 1: Claude Desktop AppOpen the Customize panel in the sidebar → browse connectors → search and add. Works in Claude Code, Claude Cowork, and Claude Chat.
Option 2: Paste into Claude CodeCopy the command below and paste it into a Claude Code conversation. Claude will run it for you.
Command
claude mcp add notion --env NOTION_TOKEN=ntn_**** -- npx -y @notionhq/notion-mcp-server

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

First thing to try

Once it’s connected, paste this into Claude:

Help me search my entire Notion workspace from inside a conversation
PrerequisitesNotion account with API access. Create integration at notion.so/my-integrations.Time to functional15 minutes (API key setup required)CostFreemium — $0 (within Notion plan limits)

Trust Signals ✓ Tested

Stars4,522Contributors22Last updated2026-06-22LicenseMIT (OK for commercial use)Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-07-20 · scanner vattempted-no-data

Data & Access

Data processingPrompts sent to Anthropic API. Enterprise/Team plans exclude training.Connects toNotion servers (official integration)

Community Pulse Active

Discussed on Hacker News, Reddit

3 mentions across 2 sources

Reviewer notes

✓ Tested review. These are observations, not a security certification.

audit 2026-07-05 stale-eval refresh: Scored from trust signals (evidence-eval-v1): 4,481 GitHub stars; 22 contributors; last commit 13d ago; license MIT.

2026-05-10: Solid for automating Notion read/writes from Claude — querying databases, drafting pages, and updating project trackers without leaving the chat. OAuth setup is straightforward if you've done Notion integrations before, but complex relational schemas often require chaining multiple queries, so don't expect single-shot results on anything with nested linked databases. High-volume workflows will hit API rate limits fast; batch or throttle accordingly. Production adoption is still thin relative to the star count, so treat this as a capable but early-stage integration rather than a hardened pipeline component.

2026-04-02: LIMITATION: OAuth only — bearer token auth not supported, blocking headless/CI use. No bulk operations. Full workspace read/write access requires careful API key scoping.

2026-03-29: SECURITY FINDING (JJ Englert, Mar 2026): Cowork connectors are scoped at the Anthropic account level, NOT the workspace level. A connector added in one Cowork workspace is accessible in ALL workspaces under the same Anthropic account. This means: (1) connectors with sensitive access (email, calendar, CRM) bleed across all projects/workspaces; (2) multi-tenant setups sharing an Anthropic account are NOT isolated at the connector level; (3) evaluate connector blast radius across the full account, not just the workspace being configured. Source: https://github.com/JJenglert1/getting-started-with-claude-cowork

Things to check

  • Notion now prioritizes its hosted remote MCP (mcp.notion.com, OAuth) and says it may sunset this local server repo; issues and PRs here are not actively monitored. Requires a Notion internal integration token (NOTION_TOKEN) — consider a read-only integration for safety. v2.0 removed the old database tools in favor of data-source tools (database_id -> data_source_id). Notion API rate limits apply, so batch high-volume automated updates.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Ease of Use
4/5
Versatility
5/5
Reliability
5/5
Security
3/5
Overall score4.35 / 5.00 SolidEvaluatedJul 2026
audit 2026-07-05 stale-eval refresh: Scored from trust signals (evidence-eval-v1): 4,481 GitHub stars; 22 contributors; last commit 13d ago; license MIT.

Related Outcomes

This tool shows up in these problem-focused recommendations.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →