@notionhq/notion-mcp-server

What it does

Official Notion MCP server that bridges Claude and other AI clients to the Notion API. Provides 22 tools for querying data sources (Notion's term for databases), retrieving page content, editing pages in Markdown format, and managing database properties and schemas. Version 2.0.0 uses Notion's latest API (2025-09-03), reorganizing database operations around data sources as the primary abstraction. Legacy database tools were replaced with new data source equivalents that accept data_source_id instead of database_id. The server requires a Notion API token and explicit per-workspace access grants for each page or database exposed to Claude.

Who it's for

Product teams, researchers, and knowledge workers using Notion as a primary workspace or knowledge base who want Claude to read, query, and update their pages and databases. Useful for automating information retrieval, content synthesis, or task management workflows spanning Notion and Claude.

Common use cases

• Query a Notion data source with filters and sorting from Claude
• Retrieve and edit Notion pages in Markdown, enabling Claude to update documentation
• Retrieve database schemas and metadata to understand available data structures
• Automate bulk updates to Notion tasks or status fields
• Move pages between different parent locations or databases

Setup pitfalls

• Requires creating an internal Notion integration and manually granting it access to specific pages and databases; without explicit access configuration, the server cannot read anything
• Version 2.0.0 introduces breaking changes: database query tools now use data source APIs with data_source_id parameters instead of database_id
• Requires NOTION_TOKEN environment variable (1 secret detected) — store securely and never commit to version control
• The local MCP server is being sunset in favor of Notion's official remote MCP; new projects should consider the remote version for ongoing support