Notion MCP Server

by MCP-Mirror

188 downloads
Not rated
GitHub

About

An MCP (Model Context Protocol) server that provides a controlled interface to the Notion API, allowing AI assistants to search, read, comment on, and create pages and databases. Designed for developers who want to let LLMs interact with Notion workspaces safely.

Details

Author
MCP-Mirror
Downloads
188
Categories
Knowledge Base

- Wraps the Notion API as an MCP server for LLMs.
- Supports searching, reading, commenting, and creating pages.
- Deliberately excludes destructive operations like deleting databases.
- Works with both npx (Node.js) and Docker.
- Allows read-only token configuration for enhanced security.

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Notion MCP Server
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Create a Notion internal integration to obtain a secret token, then add the MCP configuration to your client’s mcp.json or claude_desktop_config.json. Use either npx or Docker, providing the token via the OPENAPI_MCP_HEADERS environment variable. Connect your integration to the pages/databases you want the server to access.

API-get-user

Notion | Retrieve a user Error Responses: 400: 400

API-get-users

Notion | List all users Error Responses: 400: 400

API-get-self

Notion | Retrieve your token's bot user Error Responses: 400: Bad request

API-post-search

Notion | Search by title Error Responses: 400: Bad request

API-get-block-children

Notion | Retrieve block children Error Responses: 400: Bad request

API-patch-block-children

Notion | Append block children Error Responses: 400: Bad request

API-retrieve-a-block

Notion | Retrieve a block Error Responses: 400: Bad request

API-update-a-block

Notion | Update a block Error Responses: 400: Bad request

API-delete-a-block

Notion | Delete a block Error Responses: 400: Bad request

API-retrieve-a-page

Notion | Retrieve a page Error Responses: 400: Bad request

API-patch-page

Notion | Update page properties Error Responses: 400: Bad request

API-post-page

Notion | Create a page Error Responses: 400: Bad request

API-retrieve-a-page-property

Notion | Retrieve a page property item Error Responses: 400: Bad request

API-retrieve-a-comment

Notion | Retrieve comments Error Responses: 400: Bad request

API-create-a-comment

Notion | Create comment Error Responses: 400: Bad request

API-query-data-source

Notion | Query a data source Error Responses: 400: Bad request

API-retrieve-a-data-source

Notion | Retrieve a data source Error Responses: 400: Bad request

API-update-a-data-source

Notion | Update a data source Error Responses: 400: Bad request

API-create-a-data-source

Notion | Create a data source Error Responses: 400: Bad request

API-list-data-source-templates

Notion | List templates in a data source Error Responses: 400: Bad request

API-retrieve-a-database

Notion | Retrieve a database Error Responses: 400: Bad request

API-move-page

Notion | Move a page Error Responses: 400: Bad request

API-retrieve-page-markdown

Notion | Retrieve a page as Markdown Error Responses: 400: Bad request 403: The integration lacks the read/update content capability required for this page. 404: Page not found or not shared with the integration. 429: Rate limited.

API-update-page-markdown

Notion | Update a page's content as Markdown Error Responses: 400: Bad request 403: The integration lacks the read/update content capability required for this page. 404: Page not found or not shared with the integration. 409: Conflict (e.g. row limit exceeded). 429: Rate limited.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "notion mcp server": {
            "notionApi": {
                "command": "npx",
                "args": [
                    "-y",
                    "@notionhq/notion-mcp-server"
                ],
                "env": {
                    "OPENAPI_MCP_HEADERS": "{\"Authorization\": \"Bearer ntn_****\", \"Notion-Version\": \"2022-06-28\" }"
                }
            }
        }
    }
}

McpServers

{
    "notionApi": {
        "command": "npx",
        "args": [
            "-y",
            "@notionhq/notion-mcp-server"
        ],
        "env": {
            "OPENAPI_MCP_HEADERS": "{\"Authorization\": \"Bearer ntn_****\", \"Notion-Version\": \"2022-06-28\" }"
        }
    }
}

Notion MCP Server

notion-mcp-sm

This project implements an MCP server for the Notion API.

mcp-demo

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. Adding MCP config to your client:

Using npm:
Add the following to your .cursor/mcp.json or claude_desktop_config.json (MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json)
{
  "mcpServers": {
    "notionApi": {
      "command": "npx",
      "args": ["-y", "@notionhq/notion-mcp-server"],
      "env": {
        "OPENAPI_MCP_HEADERS": "{\"Authorization\": \"Bearer ntn_*\", \"Notion-Version\": \"2022-06-28\" }"
      }
    }
  }
}
Using Docker:
You can also run the MCP server using Docker. First, build the Docker image:
docker-compose build

Then, add the following to your .cursor/mcp.json or claude_desktop_config.json:

{
  "mcpServers": {
    "notionApi": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "OPENAPI_MCP_HEADERS={\"Authorization\": \"Bearer ntn_\", \"Notion-Version\": \"2022-06-28\"}",
        "notion-mcp-server-notion-mcp-server"
      ]
    }
  }
}

Don't forget to replace ntn_* with your integration secret. Find it from your integration configuration tab:

Copying your Integration token from the Configuration tab in the developer portal

3. Connecting content to integration:

Ensure relevant pages and databases are connected to your integration.

To do this, you'll need to visit that page, and click on the 3 dots, and select "Connect to integration".

Adding Integration Token to Notion Connections

Examples

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

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

3. You may also reference content ID directly

Get the content of page 1a6b35e6e67f802fa7e1d27686f017f2

Development

Build

npm run build

Execute

npx -y --prefix /path/to/local/notion-mcp-server @notionhq/notion-mcp-server

Publish

npm publish --access public
No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.