skillpack.co
All skills

Notion MCP Server

active

Official Notion MCP server with hosted OAuth, token-optimized Markdown responses, and 22 tools for page/database/search operations.

Connector
Composite
Complexity
businessproductivity

70/100

Trust

4.1K+

Stars

7

Evidence

1.3 MB

Repo size

Videos

Reviews, tutorials, and comparisons from the community.

Build your AI Second Brain with Notion and Claude (MCP)

Zen van Riel·2025-04-02

How to Connect Notion to Claude AI with Notion MCP | Easy Tutorial!

The Organized Notebook·2025-08-04

Notion + MCP 双厨狂喜?10 分钟速看 Notion MCP Server 实际体验

海拉鲁编程客·2025-04-16

Repo health

70/100

1d ago

Last push

120

Open issues

510

Forks

22

Contributors

Editorial verdict

#1 operating surface for product teams — 47K+ npm weekly downloads (17x Atlassian) is the strongest objective adoption signal. Notion 3.3 Custom Agents ecosystem positions MCP as multi-tool hub.

Public evidence

strongSelf-reported2026-02
Notion 3.3 Custom Agents: 21,000+ agents created in early access

Notion 3.3 Custom Agents (Feb 24, 2026) positions the MCP server as the hub of a multi-tool agent ecosystem connecting Slack, Linear, Figma, HubSpot via MCP. 21,000+ agents created in early access.

21,000+ agents in early accessNotion (official)

How does this compare?

See side-by-side metrics against other skills in the same category.

COMPARE SKILLS →

Where it wins

Official (makenotion org), MIT license

47,612 npm weekly downloads — highest real-world install adoption

Hosted OAuth — no local setup required

Token-optimized Markdown responses for LLM-native interaction

Integrated into Google ADK documentation

Where to be skeptical

Narrower scope than Atlassian (one platform vs Jira + Confluence)

Notion may sunset local MCP server in favor of remote-only

GitHub issues 'not actively monitored' per repo notice

Ranking in categories

Know a better alternative?

Submit evidence and we'll run the full pipeline.

SUBMIT →

Similar skills

Raw GitHub source

GitHub README peek

Constrained peek so you can sanity-check the source material without leaving the site.

Notion MCP Server

[!NOTE]

We’ve introduced Notion MCP, a remote MCP server with the following improvements:

  • Easy installation via standard OAuth. No need to fiddle with JSON or API tokens anymore.
  • Powerful tools tailored to AI agents, including editing pages in Markdown. These tools are designed with optimized token consumption in mind.

Learn more and get started at Notion MCP documentation.

We are prioritizing, and only providing active support for, Notion MCP (remote). As a result:

  • We may sunset this local MCP server repository in the future.
  • Issues and pull requests here are not actively monitored.
  • Please do not file issues relating to the remote MCP here; instead, contact Notion support.

notion-mcp-sm

This project implements an MCP server for the Notion API.

mcp-demo


⚠️ Version 2.0.0 breaking changes

Version 2.0.0 migrates to the Notion API 2025-09-03 which introduces data sources as the primary abstraction for databases.

What changed

Removed tools (3):

  • post-database-query - replaced by query-data-source
  • update-a-database - replaced by update-a-data-source
  • create-a-database - replaced by create-a-data-source

New tools (7):

  • query-data-source - Query a data source (database) with filters and sorts
  • retrieve-a-data-source - Get metadata and schema for a data source
  • update-a-data-source - Update data source properties
  • create-a-data-source - Create a new data source
  • list-data-source-templates - List available templates in a data source
  • move-page - Move a page to a different parent location
  • retrieve-a-database - Get database metadata including its data source IDs

Parameter changes:

  • All database operations now use data_source_id instead of database_id
  • Search filter values changed from ["page", "database"] to ["page", "data_source"]
  • Page creation now supports both page_id and database_id parents (for data sources)
Do I need to migrate?

No code changes required. MCP tools are discovered automatically when the server starts. When you upgrade to v2.0.0, AI clients will automatically see the new tool names and parameters. The old database tools are no longer available.

If you have hardcoded tool names or prompts that reference the old database tools, update them to use the new data source tools:

Old Tool (v1.x)New Tool (v2.0)Parameter Change
post-database-queryquery-data-sourcedatabase_iddata_source_id
update-a-databaseupdate-a-data-sourcedatabase_iddata_source_id
create-a-databasecreate-a-data-sourceNo change (uses parent.page_id)

Note: retrieve-a-database is still available and returns database metadata including the list of data source IDs. Use retrieve-a-data-source to get the schema and properties of a specific data source.

Total tools now: 22 (was 19 in v1.x)


Installation

1. Setting up integration in Notion

Go to https://www.notion.so/profile/integrations and create a new internal integration or select an existing one.

Creating a Notion Integration token

While we limit the scope of Notion API's exposed (for example, you will not be able to delete databases via MCP), there is a non-zero risk to workspace data by exposing it to LLMs. Security-conscious users may want to further configure the Integration's Capabilities.

For example, you can create a read-only integration token by giving only "Read content" access from the "Configuration" tab:

Notion Integration Token Capabilities showing Read content checked

2. Connecting content to integration

Ensure relevant pages and databases are connected to your integration.

To do this, visit the Access tab in your internal integration settings. Edit access and select the pages you'd like to use.

Integration Access tab

Edit integration access

Alternatively, you can grant page access individually. You'll need to visit the target page, and click on the 3 dots, and select "Connect to integration".

Adding Integration Token to Notion Connections

3. Adding MCP config to your client

Using npm
Cursor & Claude

Add the following to your .cursor/mcp.json or claude_desktop_config.json (MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json)

Option 1: Using NOTION_TOKEN (recommended)
{
  "mcpServers": {
    "notionApi": {
      "command": "npx",
      "args": ["-y", "@notionhq/notion-mcp-server"],
      "env": {
        "NOTION_TOKEN": "ntn_****"
      }
    }
  }
}
Option 2: Using OPENAPI_MCP_HEADERS (for advanced use cases)
{
  "mcpServers": {
    "notionApi": {
      "command": "npx",
      "args": ["-y", "@notionhq/notion-mcp-server"],
      "env": {
        "OPENAPI_MCP_HEADERS": "{\"Authorization\": \"Bearer ntn_****\", \"Notion-Version\": \"2025-09-03\" }"
      }
    }
  }
}
Zed
View on GitHub →