Notion MCP Server

npx @notionhq/notion-mcp-server --transport http

Notion MCP Server

The Notion MCP Server is the official MCP integration maintained by Notion (makenotion) that gives AI assistants read/write access to Notion workspaces. It covers pages, databases (now called data sources in v2.0), blocks, search, and page movement. As of 2026, Notion prioritizes a remote MCP server with OAuth authentication and no local setup, while the local npm package remains available for self-managed or stdio-based deployments.

Notion workspaces hold documentation, roadmaps, project trackers, and wikis that teams reference constantly. With the MCP server, that content is addressable from Claude: you can read a spec page, create a new database row, or reorganize pages without switching windows.

For productivity teams managing documentation in Notion, this integration is the most direct path to AI-assisted content creation. The Filesystem MCP server handles local files in the same workflow when your assets span both disk and Notion.

How does it work?

Notion hosts a remote MCP server at the URL documented at developers.notion.com/docs/mcp. Connect via OAuth in one step: no JSON config files, no token management. For local or CI environments, run npx @notionhq/notion-mcp-server and export NOTION_API_KEY with a Notion internal integration token.

Data sources (v2.0 API)

Version 2.0.0 migrated to the Notion API 2025-09-03, which introduces data sources as the primary database abstraction. The new tools are:

Tool	What it does
query-data-source	Query a database with filters and sorts
retrieve-a-data-source	Fetch schema and metadata for a database
create-a-data-source	Create a new database
update-a-data-source	Modify database properties
list-data-source-templates	List templates available in a data source

Page operations

Tool	What it does
retrieve-a-page	Fetch page title, properties, and content
create-a-page	Create a page in a database or as a child page
update-a-page	Update page properties
append-block-children	Add blocks (paragraphs, headings, code, callouts)
move-page	Move a page to a new parent location
search	Full-text search across accessible pages and databases

When to use it

Use the Notion MCP server when you want Claude to read from or write to a Notion workspace as part of a larger workflow: generating meeting notes from a transcript and saving them to a Notion page, querying a project database for open tasks, or building a content pipeline where Claude populates database rows from structured data. The query-data-source tool handles filtered, sorted queries across large databases — Claude can retrieve only the rows matching a date range or status value.

For teams where content also lives in local files, combining Notion MCP with the Filesystem MCP server lets Claude bridge disk and workspace in a single session.

Frequently asked questions

Do I need to share each Notion page with the integration individually?

Yes. Notion’s API requires that each page or database be explicitly shared with the integration. In your Notion workspace, open a page, click the three-dot menu, and select Add connections to share it with your integration. Pages not shared with the integration will not appear in search results or be accessible by any tool.

Is the local npm server being discontinued?

Notion has stated it is prioritizing the remote MCP server and may sunset the local npm repository in the future. For production use, the remote server is recommended. Issues and pull requests on the npm repository are not actively monitored. Self-managed deployments that need local stdio mode should pin a specific npm version to avoid breaking changes.

What Notion plan is required to use the MCP server?

The Notion API is available on Free plans with limited API call quotas. Paid plans (Plus, Business, Enterprise) have higher rate limits. For high-frequency workflows such as automated database updates from a CI pipeline, a paid plan avoids hitting the free tier rate cap.