Notion MCP Server
Provides tools for interacting with Notion's API, enabling AI agents to manage pages, databases, and comments within Notion workspaces programmatically.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Notion MCP Server find my meeting notes from last week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Notion MCP Server
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 token anymore.
Powerful tools tailored to AI agents. These tools are designed with optimized token consumption in mind.
Learn more and try it out here
This project implements an MCP server for the Notion API.
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\": \"2022-06-28\" }"
}
}
}
}Zed
Add the following to your settings.json
{
"context_servers": {
"some-context-server": {
"command": {
"path": "npx",
"args": ["-y", "@notionhq/notion-mcp-server"],
"env": {
"OPENAPI_MCP_HEADERS": "{\"Authorization\": \"Bearer ntn_****\", \"Notion-Version\": \"2022-06-28\" }"
}
},
"settings": {}
}
}
}Using Docker:
There are two options for running the MCP server with Docker:
Option 1: Using the official Docker Hub image:
Add the following to your .cursor/mcp.json or claude_desktop_config.json:
Using NOTION_TOKEN (recommended):
{
"mcpServers": {
"notionApi": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e", "NOTION_TOKEN",
"mcp/notion"
],
"env": {
"NOTION_TOKEN": "ntn_****"
}
}
}
}Using OPENAPI_MCP_HEADERS (for advanced use cases):
{
"mcpServers": {
"notionApi": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e", "OPENAPI_MCP_HEADERS",
"mcp/notion"
],
"env": {
"OPENAPI_MCP_HEADERS": "{\"Authorization\":\"Bearer ntn_****\",\"Notion-Version\":\"2022-06-28\"}"
}
}
}
}This approach:
Uses the official Docker Hub image
Properly handles JSON escaping via environment variables
Provides a more reliable configuration method
Option 2: Building the Docker image locally:
You can also build and run the Docker image locally. First, build the Docker image:
docker compose buildThen, add the following to your .cursor/mcp.json or claude_desktop_config.json:
Using NOTION_TOKEN (recommended):
{
"mcpServers": {
"notionApi": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"NOTION_TOKEN=ntn_****",
"notion-mcp-server"
]
}
}
}Using OPENAPI_MCP_HEADERS (for advanced use cases):
{
"mcpServers": {
"notionApi": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"OPENAPI_MCP_HEADERS={\"Authorization\": \"Bearer ntn_****\", \"Notion-Version\": \"2022-06-28\"}",
"notion-mcp-server"
]
}
}
}Don't forget to replace ntn_**** with your integration secret. Find it from your integration configuration tab:
Installing via Smithery
To install Notion API Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @makenotion/notion-mcp-server --client claudeTransport Options
The Notion MCP Server supports two transport modes:
STDIO Transport (Default)
The default transport mode uses standard input/output for communication. This is the standard MCP transport used by most clients like Claude Desktop.
# Run with default stdio transport
npx @notionhq/notion-mcp-server
# Or explicitly specify stdio
npx @notionhq/notion-mcp-server --transport stdioStreamable HTTP Transport
For web-based applications or clients that prefer HTTP communication, you can use the Streamable HTTP transport:
# Run with Streamable HTTP transport on port 3000 (default)
npx @notionhq/notion-mcp-server --transport http
# Run on a custom port
npx @notionhq/notion-mcp-server --transport http --port 8080
# Run with a custom authentication token
npx @notionhq/notion-mcp-server --transport http --auth-token "your-secret-token"When using Streamable HTTP transport, the server will be available at http://0.0.0.0:<port>/mcp.
Authentication
The Streamable HTTP transport requires bearer token authentication for security. You have three options:
Option 1: Auto-generated token (recommended for development)
npx @notionhq/notion-mcp-server --transport httpThe server will generate a secure random token and display it in the console:
Generated auth token: a1b2c3d4e5f6789abcdef0123456789abcdef0123456789abcdef0123456789ab
Use this token in the Authorization header: Bearer a1b2c3d4e5f6789abcdef0123456789abcdef0123456789abcdef0123456789abOption 2: Custom token via command line (recommended for production)
npx @notionhq/notion-mcp-server --transport http --auth-token "your-secret-token"Option 3: Custom token via environment variable (recommended for production)
AUTH_TOKEN="your-secret-token" npx @notionhq/notion-mcp-server --transport httpThe command line argument --auth-token takes precedence over the AUTH_TOKEN environment variable if both are provided.
Making HTTP Requests
All requests to the Streamable HTTP transport must include the bearer token in the Authorization header:
# Example request
curl -H "Authorization: Bearer your-token-here" \
-H "Content-Type: application/json" \
-H "mcp-session-id: your-session-id" \
-d '{"jsonrpc": "2.0", "method": "initialize", "params": {}, "id": 1}' \
http://localhost:3000/mcpNote: Make sure to set either the NOTION_TOKEN environment variable (recommended) or the OPENAPI_MCP_HEADERS environment variable with your Notion integration token when using either transport mode.
Examples
Using the following instruction
Comment "Hello MCP" on page "Getting started"AI will correctly plan two API calls, v1/search and v1/comments, to achieve the task
Similarly, the following instruction will result in a new page named "Notion MCP" added to parent page "Development"
Add a page titled "Notion MCP" to page "Development"You may also reference content ID directly
Get the content of page 1a6b35e6e67f802fa7e1d27686f017f2Development
Build
npm run buildExecute
npx -y --prefix /path/to/local/notion-mcp-server @notionhq/notion-mcp-serverPublish
npm publish --access publicAvailable Tools
19 toolsAPI-create-a-commentC
Notion | Create comment
Inputs: parent (required), rich_text (required).
API-create-a-databaseC
Notion | Create a database
Inputs: parent (required), properties (required), title.
API-delete-a-blockC
Notion | Delete a block
Inputs: block_id (required).
API-get-block-childrenC
Notion | Retrieve block children
Inputs: block_id (required), page_size, start_cursor.
API-get-selfB
Notion | Retrieve your token's bot user
Inputs: no named parameters.
API-get-userC
Notion | Retrieve a user
Inputs: user_id (required).
API-get-usersC
Notion | List all users
Inputs: page_size, start_cursor.
API-patch-block-childrenC
Notion | Append block children
Inputs: block_id (required), children (required), after.
API-patch-pageC
Notion | Update page properties
Inputs: page_id (required), archived, cover, icon, +2 more.
API-post-database-queryC
Notion | Query a database
Inputs: database_id (required), archived, filter, filter_properties, +4 more.
API-post-pageC
Notion | Create a page
Inputs: parent (required), properties (required), children, cover, +1 more.
API-post-searchC
Notion | Search by title
Inputs: filter, page_size, query, sort, +1 more.
API-retrieve-a-blockC
Notion | Retrieve a block
Inputs: block_id (required).
API-retrieve-a-commentC
Notion | Retrieve comments
Inputs: block_id (required), page_size, start_cursor.
API-retrieve-a-databaseC
Notion | Retrieve a database
Inputs: database_id (required).
API-retrieve-a-pageC
Notion | Retrieve a page
Inputs: page_id (required), filter_properties.
API-retrieve-a-page-propertyC
Notion | Retrieve a page property item
Inputs: page_id (required), property_id (required), page_size, start_cursor.
API-update-a-blockC
Notion | Update a block
Inputs: block_id (required), archived, type.
API-update-a-databaseC
Notion | Update a database
Inputs: database_id (required), description, properties, title.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 19 tools
Most tools have distinct purposes targeting specific Notion resources like blocks, pages, databases, comments, and users, with clear action verbs. However, 'API-retrieve-a-block' and 'API-get-block-children' could be slightly confusing as both involve blocks, though one fetches a single block and the other its children.
Tool names follow a consistent 'API-verb-a-noun' pattern with minor deviations like 'API-get-users' (plural) and 'API-post-database-query' (includes 'query'). The pattern is mostly uniform, making tools predictable and readable, though not perfectly standardized.
With 19 tools, the count is slightly high but reasonable for Notion's broad API scope covering blocks, pages, databases, comments, and users. It provides comprehensive coverage without being overwhelming, though it borders on the heavy side.
The tool set offers complete CRUD and lifecycle coverage for Notion's core resources: create, retrieve, update, and delete operations for blocks, pages, databases, and comments, plus user management and search. No obvious gaps exist for typical agent workflows in this domain.
Maintenance
Related MCP Connectors
Persistent docs and memory for AI agents — read, write, organize & search a shared workspace.
Governed memory and workspace for any AI: tasks, calendar, mail and pages, with per-action consent.
Persistent memory and knowledge management for AI agents with semantic search and 50+ tools.
Query and update Teable records, manage tables, and access the Teable API with AI agents.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables interaction with Notion workspaces through the Notion API. Supports creating, retrieving, and updating Notion pages and their properties, allowing users to manage Notion content through natural language.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Notion workspaces through the Notion API. Supports searching, reading, creating pages, and querying databases with filters and sorting capabilities.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Notion workspaces through the Notion API, allowing them to search, read, create, and comment on pages and databases with optimized token consumption.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Notion workspaces through the Notion API, allowing them to search, read, create, update pages and databases, and manage comments using natural language commands.MIT