47,612 weekly downloads vs 604 for Google Workspace MCP. Highest real-world install adoption of any business MCP server.
Notion MCP Server
activeOfficial Notion MCP server with hosted OAuth, token-optimized Markdown responses, and 22 tools for page/database/search operations.
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)
How to Connect Notion to Claude AI with Notion MCP | Easy Tutorial!
Notion + MCP 双厨狂喜?10 分钟速看 Notion MCP Server 实际体验
Repo health
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.
Source
GitHub: makenotion/notion-mcp-server
Public evidence
4,054 stars, official org, MIT license. v2.0/v2.1 shows maturation with breaking changes handled. Hosted OAuth since July 2025.
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.
Notion MCP Server integrated into Google ADK documentation as a featured MCP integration example. Cross-platform endorsement.
Remote: '>95% triage accuracy, 25%+ tickets resolved autonomously.' Named enterprise customers with quantified production outcomes.
Major security vendor building official MCP integration with Notion. Platform flywheel extending beyond productivity into enterprise security.
Page-level granularity only — no block editing, no file access, auth expires weekly, no database view/filter. Third-party StackOne (27+ tools) fills gaps.
How does this compare?
See side-by-side metrics against other skills in the same category.
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.
Similar skills

PostHog MCP
73Official PostHog MCP — product analytics, feature flags, experiments, error tracking, and usage insights via MCP. Integrated into PostHog monorepo Jan 2026. #5 all-time globally on PulseMCP (5.7M visits).
Firecrawl MCP Server
70Official Firecrawl MCP for scraping, extraction, and deep research workflows. 50K+ npm weekly downloads, backed by $14.5M Series A.
Slack MCP Server
66Community MCP server for Slack alongside official Slack MCP (GA Feb 2026). Enables agent access to channel search, messaging, and coordination.
Exa MCP Server
62Official Exa MCP for fast web search and crawling when the workflow is search-first rather than page-ops-first.
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.
This project implements an MCP server for the Notion API.
⚠️ 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 byquery-data-sourceupdate-a-database- replaced byupdate-a-data-sourcecreate-a-database- replaced bycreate-a-data-source
New tools (7):
query-data-source- Query a data source (database) with filters and sortsretrieve-a-data-source- Get metadata and schema for a data sourceupdate-a-data-source- Update data source propertiescreate-a-data-source- Create a new data sourcelist-data-source-templates- List available templates in a data sourcemove-page- Move a page to a different parent locationretrieve-a-database- Get database metadata including its data source IDs
Parameter changes:
- All database operations now use
data_source_idinstead ofdatabase_id - Search filter values changed from
["page", "database"]to["page", "data_source"] - Page creation now supports both
page_idanddatabase_idparents (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-query | query-data-source | database_id → data_source_id |
update-a-database | update-a-data-source | database_id → data_source_id |
create-a-database | create-a-data-source | No change (uses parent.page_id) |
Note:
retrieve-a-databaseis still available and returns database metadata including the list of data source IDs. Useretrieve-a-data-sourceto 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.

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:

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.


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".

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\" }"
}
}
}
}