Claude + Notion Integration: Setup, MCP, Workflows
Set up Claude with Notion for knowledge management, MCP-style retrieval, meeting notes, SOPs, client research, and team workflows.
In this article
Short answer: the best Claude + Notion setup
Use Notion integrations and MCP-style access when your team needs Claude to work from living docs: meeting notes, project plans, knowledge bases, content calendars, SOPs, and client research. Start with read-only access, then expand permissions only after the workflow is proven.
Implementation checklist
FAQ
Why Integrate Claude with Notion
Most teams have valuable context trapped in Notion:
- Product documentation and decisions
- Client background and history
- Process runbooks and SOPs
- Meeting notes and discussions
- Research and analysis
Without integration:
- You manually search Notion when working with Claude
- Context gets copied and pasted
- Knowledge stays siloed
- Claude can't reference institutional memory
With integration:
- Claude reads your Notion workspace directly
- Answers reference your actual documentation
- Can create and update pages programmatically
- Institutional knowledge becomes queryable
Setup: Notion MCP Server
Prerequisites
- Claude Code installed
- Node.js 16+ on your system
- Notion workspace with admin access
- Basic command line familiarity
Step 1: Create Notion Integration
- Read content: Yes - Update content: Yes - Insert content: Yes
This token lets Claude access your Notion workspace.
Step 2: Share Pages with Integration
The integration can only access pages you explicitly share:
Step 3: Install MCP Server
Open terminal and run:
<code class="language-bash">npm install -g @anthropic-ai/mcp-notion</code>
This installs the Notion MCP server globally.
Step 4: Configure Claude Code
Add to your Claude Code MCP configuration file:
Read the original source on github.com
<code class="language-json">{
<p>"mcpServers": { "notion": { "command": "mcp-notion", "env": { "NOTION_API_KEY": "your_integration_token_here" } } } }</code>Replace your_integration_token_here with the token from Step 1.
Step 5: Restart Claude Code
Quit and restart Claude Code completely.
Claude API Reference: Official API documentation for Claude integration Learn more
To verify it's working, ask Claude: "What databases do you have access to in Notion?"
Claude should list your Notion databases.
Core Capabilities
Once configured, Claude can:
Model Context Protocol: Official MCP documentation and server registry Learn more
1. Search Your Workspace
"Search our Notion for customer feedback about the mobile app from the last quarter."
Claude:
- Searches across all shared pages
- Filters by date and keywords
- Returns relevant pages and excerpts
2. Query Databases
"Show me all high-priority bugs assigned to the backend team."
Claude:
- Queries your issue database
- Filters by properties (priority, assignee)
- Returns structured results
3. Read Page Content
"What does our onboarding runbook say about access provisioning?"
Claude:
- Finds the runbook page
- Reads specific sections
- Quotes relevant content
4. Create Pages
"Create a project brief page for the Q2 marketing campaign in our Projects database."
Claude:
- Creates new page in specified database
- Sets properties (status, owner, dates)
- Adds structured content
5. Update Existing Pages
"Update the mobile app project status to 'In Review' and add a note that testing is complete."
Claude:
- Finds the project page
- Updates status property
- Appends note to page content
Practical Workflows
Workflow 1: Client Research
Claude:
- Searches for "Acme Corp" across workspace
- Finds account page, project pages, meeting notes
- Summarizes:
- Active projects and status - Recent challenges or requests - Key contacts and relationships
Workflow 2: Documentation Creation
Claude:
- Queries support tickets database for API issues
- Reads related engineering notes
- Identifies patterns and common problems
- Creates structured troubleshooting guide page
- Organizes by symptom → diagnosis → solution
Workflow 3: Project Status Reporting
Claude:
- Queries projects database
- Filters for active status
- Reads recent updates and comments
- Generates summary report with:
- Yellow (at risk): with reasons - Red (blocked): with blockers identified - Key upcoming milestones
Workflow 4: Meeting Preparation
Claude:
- Finds previous meeting notes
- Extracts action items
- Checks project database for feature status
- Creates new meeting page with:
- Feature updates since last meeting - Suggested agenda topics
Workflow 5: Onboarding Automation
Claude:
- Searches workspace for relevant pages
- Returns organized list:
- Engineering workflow pages - Team handbook sections - Who to ask for specific questions
Advanced Workflows
Automated Knowledge Base Updates
In Claude Code:
"I just refactored the authentication system. Update our API documentation page in Notion with the new endpoint structure and deprecation notes."
Claude:
- Analyzes code changes
- Finds API documentation page
- Updates endpoint documentation
- Adds deprecation warnings
- Creates changelog entry
Cross-Database Analysis
"Analyze our customer feedback database and correlate it with our roadmap database. Which requested features are already planned, and which are missing?"
Claude:
- Queries feedback database
- Extracts feature requests
- Queries roadmap database
- Identifies gaps
- Generates report showing:
- Requested features not planned - Frequency of unplanned requests
Automated Status Updates
"Update all client project pages with this week's progress based on our Linear issues."
Note: Requires both Notion and Linear integrations
Claude:
- Queries Linear for completed issues
- Maps issues to client projects
- Updates each Notion project page
- Adds progress notes
- Updates status properties
Organization Best Practices
Structure Your Notion for Claude
Claude works better when databases have predictable structure:
- Use standard property names across databases (Status, Owner, Priority)
- Keep property types consistent
- Add descriptions to databases explaining their purpose
Make a page listing:
- What databases exist and what they contain
- Naming conventions
- How to query common information
- Important pages and where to find things
Give Claude access to this page as a "map" of your workspace.
"Project" is vague, "Q1 2026 - Acme Corp - Platform Migration" is searchable and clear.
Claude can follow links and understand relationships:
- Link related pages
- Use tags for categorization
- Create bi-directional links
Security Considerations
Only connect pages Claude actually needs:
- Share team workspaces and documentation
- Don't share sensitive HR or financial data
- Don't share personal pages
Notion's integration system is designed for this:
- Each page must be explicitly connected
- You control exactly what Claude sees
- Can revoke access anytime
Periodically generate new integration tokens:
- Every 6 months for active use
- Immediately if token might be compromised
- When team members with access leave
Check which pages are shared with the integration:
- Remove connections to outdated pages
- Verify only appropriate content is accessible
- Review who can modify integration settings
Troubleshooting
- Verify MCP server is in configuration file
- Check integration token is correct
- Ensure pages are shared with integration
- Restart Claude Code
- Check page is shared with "Claude MCP" integration
- Verify page isn't archived
- Try searching with different keywords
- Confirm integration has "Update content" capability
- Check you have edit access to the page
- Verify page isn't locked
- Large workspaces take longer to search
- Be specific in queries to narrow scope
- Consider organizing with clear database structure
Quick Takeaway
The Notion MCP server turns your Notion workspace into Claude's long-term memory. Setup takes 15 minutes: create integration, install MCP server, configure Claude Code.
Key workflows: client research, documentation generation, project status reporting, meeting preparation, and onboarding automation.
Best practice: organize Notion with Claude in mind - consistent structure, clear naming, appropriate access controls.
For teams with significant knowledge in Notion, this integration is transformative - institutional memory becomes instantly queryable and actionable.
Get the Claude playbook in your inbox.
One weekly email for Claude and Claude Code users. Real workflows, no hype. Subscribe and we send you The Claude Power-User Cheatsheet.
— ¶ —
Luke Thompson
Luke Thompson is the founder of The Operations Guide, LLC and editor of The Claude Insider. Based in Jonesborough, Tennessee, he has spent years building AI-augmented business systems and automation workflows for operators and teams. He began working with large language models in production well before the current wave of consumer AI tools, integrating them into client workflows, content pipelines, and operational infrastructure. At The Claude Insider, he writes about Claude with the specificity of someone who uses it daily as a professional tool — not as a reviewer or commentator, but as a builder. His coverage focuses on what actually works: prompt patterns, API integration strategies, agentic workflows, and the real-world tradeoffs that practitioners face. He is not affiliated with Anthropic, PBC.
Articles are researched and drafted with AI assistance, reviewed and edited by Luke Thompson.
Know where AI can pay off in your company.
Take the free two-minute AI Readiness Assessment. See your score, the two gaps holding you back, and the next move worth making.
