How to Connect Notion to Claude — and Keep Your Workspace Clean
Notion is your team's second brain. Claude can search it, add to it, and structure it — but you need to decide exactly what it's allowed to change before the first request goes through.
Notion is where teams keep their most important knowledge — meeting notes, project wikis, SOPs, roadmaps. Connecting Claude to your Notion workspace means AI can read, search, and write within that knowledge base. It also means AI can delete blocks, overwrite pages, and restructure databases if the permissions aren't right.
This guide shows you how to connect Claude to Notion through Stow, so the AI gets a precise, policy-controlled presence in your workspace — not a blank check.
What the Setup Should Look Like
With Stow in the middle, Claude can't touch your workspace without going through your permission policy first:
Without this layer, a Notion integration token grants broad workspace access. Stow lets you enforce exactly which operations are allowed, which require your approval, and which are blocked entirely.
Why Notion Needs Careful Permission Scoping
Notion's data structure is hierarchical — pages contain blocks, blocks contain content, databases contain records. This means a single misdirected write operation can affect more than you expect:
Step 1: Connect Notion in Stow
Start inside your Stow dashboard:
- Navigate to Connected Services
- Click Add New Service
- Select Notion from the directory
- Enter your Notion Integration Token (generated in your Notion workspace settings under Integrations)
- Click Save to complete the connection
Once connected, Claude has no Notion access yet. Every capability is opt-in and enforced by Stow.
Step 2: Configure Notion Permissions
Notion permissions in Stow map cleanly onto the workspace hierarchy. Configure each layer separately — pages, databases, blocks, and search all have independent controls.
Recommended Starting Configuration
Read Users is off by default — and it should stay that way. Claude doesn't need to know who's in your workspace to read and write content. Enabling it unnecessarily expands the data the integration can access.
Step 3: Connect Claude to Stow
Wire Claude Desktop into the Stow MCP layer:
- Open Claude Desktop and click Customize in the sidebar
- Go to Connectors → Add Custom Connector
- Name it (e.g., "Stow") and paste the connector URL:
https://mcp.stowprotect.com - Click Add, then Connect — Claude initiates the OAuth flow automatically
Step 4: Start Using Notion in Claude
With the integration active, you can use prompts like:
When Claude attempts to Update an existing page or block, Stow pauses and surfaces it in your approval queue. Claude shows you what it intends to change — you approve or deny before the workspace is touched.
How Notion's Structure Maps to Risk
Read & Search
Reading pages, querying databases, executing search — no content changes. Safe default for all AI workflows.
Create & Append
Adding new pages or appending blocks to existing ones. Additive only — doesn't overwrite existing content.
Update & Delete
Modifying or removing existing content. These operations are hard to reverse — require approval or stay off.
What Gets Logged
Every Notion operation Claude attempts is recorded in your Stow Activity Log — including what action was taken, which page or database was involved, and whether it was allowed or denied.
No Page Content Is Ever Stored
Stow's Zero-Retention policy covers all Notion data:
- Page and block contents are stripped before reaching the database
- Notion API responses are sanitized to metadata only
- Integration tokens are masked and never persisted in plain text
Give Claude a Precise Notion Presence
Claude can genuinely help with your Notion workspace — summarizing long wikis, drafting new documentation, querying project databases. None of that requires giving it the ability to delete content or read your entire user list. With Stow, Claude gets exactly the workspace access it needs — and nothing it doesn't.
Stow Security Team
April 19, 2026