@mieubrisse/notion-mcp-server 2.0.0

package/.devcontainer/devcontainer.json

@@ -0,0 +1,4 @@
+{
+  "image": "mcr.microsoft.com/devcontainers/universal:2",
+  "features": {}
+}

package/.dockerignore

@@ -0,0 +1,3 @@
+node_modules
+Dockerfile
+docker-compose.yml

package/.github/pull_request_template.md

@@ -0,0 +1,8 @@
+## Description
+
+## How was this change tested?
+
+- [ ] Automated test (unit, integration, etc.)
+- [ ] Manual test (provide reproducible testing steps below)
+
+## Screenshots

package/.github/workflows/ci.yml

@@ -0,0 +1,42 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [20.x, 22.x]
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8
+
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run build
+        run: npm run build
+
+      - name: Run tests
+        run: npm test
+
+      - name: Check for uncommitted changes
+        run: |
+          if [ -n "$(git status --porcelain)" ]; then
+            echo "Error: Uncommitted changes detected after build"
+            git status --porcelain
+            exit 1
+          fi

package/Dockerfile

@@ -0,0 +1,36 @@
+# syntax=docker/dockerfile:1
+
+# Use Node.js LTS as the base image
+FROM node:20-slim AS builder
+
+# Set working directory
+WORKDIR /app
+
+# Copy package.json and package-lock.json
+COPY package*.json ./
+
+# Install dependencies
+RUN --mount=type=cache,target=/root/.npm npm ci --ignore-scripts --omit-dev
+
+# Copy source code
+COPY . .
+
+# Build the package
+RUN --mount=type=cache,target=/root/.npm npm run build
+
+# Install package globally
+RUN --mount=type=cache,target=/root/.npm npm link
+
+# Minimal image for runtime
+FROM node:20-slim
+
+# Copy built package from builder stage
+COPY scripts/notion-openapi.json /usr/local/scripts/
+COPY --from=builder /usr/local/lib/node_modules/@notionhq/notion-mcp-server /usr/local/lib/node_modules/@notionhq/notion-mcp-server
+COPY --from=builder /usr/local/bin/notion-mcp-server /usr/local/bin/notion-mcp-server
+
+# Set default environment variables
+ENV OPENAPI_MCP_HEADERS="{}"
+
+# Set entrypoint
+ENTRYPOINT ["notion-mcp-server"]

package/LICENSE

@@ -0,0 +1,7 @@
+Copyright (c) 2025 Notion Labs, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

package/README.md

@@ -0,0 +1,412 @@
+# 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](https://developers.notion.com/docs/mcp).
+>
+> 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](https://github.com/user-attachments/assets/6c07003c-8455-4636-b298-d60ffdf46cd8)
+
+This project implements an [MCP server](https://spec.modelcontextprotocol.io/) for the [Notion API](https://developers.notion.com/reference/intro).
+
+![mcp-demo](https://github.com/user-attachments/assets/e3ff90a7-7801-48a9-b807-f7dd47f0d3d6)
+
+---
+
+## ⚠️ 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 (4):**
+
+- `post-database-query` - replaced by `query-data-source`
+- `retrieve-a-database` - replaced by `retrieve-a-data-source`
+- `update-a-database` - replaced by `update-a-data-source`
+- `create-a-database` - replaced by `create-a-data-source`
+
+**New tools (6):**
+
+- `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
+
+**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-query` | `query-data-source` | `database_id` → `data_source_id` |
+| `retrieve-a-database` | `retrieve-a-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`) |
+
+**Total tools now: 21** (was 19 in v1.x)
+
+---
+
+### Installation
+
+#### 1. Setting up integration in Notion
+
+Go to [https://www.notion.so/profile/integrations](https://www.notion.so/profile/integrations) and create a new **internal** integration or select an existing one.
+
+![Creating a Notion Integration token](docs/images/integrations-creation.png)
+
+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](docs/images/integrations-capabilities.png)
+
+#### 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](docs/images/integration-access.png)
+
+![Edit integration access](docs/images/page-access-edit.png)
+
+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](docs/images/connections.png)
+
+#### 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)
+
+```json
+{
+  "mcpServers": {
+    "notionApi": {
+      "command": "npx",
+      "args": ["-y", "@notionhq/notion-mcp-server"],
+      "env": {
+        "NOTION_TOKEN": "ntn_****"
+      }
+    }
+  }
+}
+```
+
+###### Option 2: Using OPENAPI_MCP_HEADERS (for advanced use cases)
+
+```json
+{
+  "mcpServers": {
+    "notionApi": {
+      "command": "npx",
+      "args": ["-y", "@notionhq/notion-mcp-server"],
+      "env": {
+        "OPENAPI_MCP_HEADERS": "{\"Authorization\": \"Bearer ntn_****\", \"Notion-Version\": \"2025-09-03\" }"
+      }
+    }
+  }
+}
+```
+
+###### Zed
+
+Add the following to your `settings.json`
+
+```json
+{
+  "context_servers": {
+    "some-context-server": {
+      "command": {
+        "path": "npx",
+        "args": ["-y", "@notionhq/notion-mcp-server"],
+        "env": {
+          "OPENAPI_MCP_HEADERS": "{\"Authorization\": \"Bearer ntn_****\", \"Notion-Version\": \"2025-09-03\" }"
+        }
+      },
+      "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):
+
+```json
+{
+  "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):
+
+```json
+{
+  "mcpServers": {
+    "notionApi": {
+      "command": "docker",
+      "args": [
+        "run",
+        "--rm",
+        "-i",
+        "-e", "OPENAPI_MCP_HEADERS",
+        "mcp/notion"
+      ],
+      "env": {
+        "OPENAPI_MCP_HEADERS": "{\"Authorization\":\"Bearer ntn_****\",\"Notion-Version\":\"2025-09-03\"}"
+      }
+    }
+  }
+}
+```
+
+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:
+
+```bash
+docker compose build
+```
+
+Then, add the following to your `.cursor/mcp.json` or `claude_desktop_config.json`
+
+Using NOTION_TOKEN (recommended):
+
+```json
+{
+  "mcpServers": {
+    "notionApi": {
+      "command": "docker",
+      "args": [
+        "run",
+        "--rm",
+        "-i",
+        "-e",
+        "NOTION_TOKEN=ntn_****",
+        "notion-mcp-server"
+      ]
+    }
+  }
+}
+```
+
+Using OPENAPI_MCP_HEADERS (for advanced use cases):
+
+```json
+{
+  "mcpServers": {
+    "notionApi": {
+      "command": "docker",
+      "args": [
+        "run",
+        "--rm",
+        "-i",
+        "-e",
+        "OPENAPI_MCP_HEADERS={\"Authorization\": \"Bearer ntn_****\", \"Notion-Version\": \"2025-09-03\"}",
+        "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](https://github.com/user-attachments/assets/67b44536-5333-49fa-809c-59581bf5370a)
+
+### Transport 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.
+
+```bash
+# Run with default stdio transport
+npx @notionhq/notion-mcp-server
+
+# Or explicitly specify stdio
+npx @notionhq/notion-mcp-server --transport stdio
+```
+
+#### Streamable HTTP transport
+
+For web-based applications or clients that prefer HTTP communication, you can use the Streamable HTTP transport:
+
+```bash
+# 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)
+
+```bash
+npx @notionhq/notion-mcp-server --transport http
+```
+
+The server will generate a secure random token and display it in the console:
+
+```text
+Generated auth token: a1b2c3d4e5f6789abcdef0123456789abcdef0123456789abcdef0123456789ab
+Use this token in the Authorization header: Bearer a1b2c3d4e5f6789abcdef0123456789abcdef0123456789abcdef0123456789ab
+```
+
+###### Option 2: Custom token via command line (recommended for production)
+
+```bash
+npx @notionhq/notion-mcp-server --transport http --auth-token "your-secret-token"
+```
+
+###### Option 3: Custom token via environment variable (recommended for production)
+
+```bash
+AUTH_TOKEN="your-secret-token" npx @notionhq/notion-mcp-server --transport http
+```
+
+The 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:
+
+```bash
+# 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/mcp
+```
+
+**Note:** 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
+
+1. Using the following instruction
+
+```text
+Comment "Hello MCP" on page "Getting started"
+```
+
+   AI will correctly plan two API calls, `v1/search` and `v1/comments`, to achieve the task
+
+1. Similarly, the following instruction will result in a new page named "Notion MCP" added to parent page "Development"
+
+```text
+Add a page titled "Notion MCP" to page "Development"
+```
+
+1. You may also reference content ID directly
+
+```text
+Get the content of page 1a6b35e6e67f802fa7e1d27686f017f2
+```
+
+### Development
+
+#### Build & test
+
+```bash
+npm run build
+npm test
+```
+
+#### Execute
+
+```bash
+npx -y --prefix /path/to/local/notion-mcp-server @notionhq/notion-mcp-server
+```
+
+Testing changes locally in Cursor:
+
+1. Run `npm link` command from repository root to create a machine-global symlink to the `notion-mcp-server` package.
+2. Merge the configuration snippet below into Cursor's `mcp.json` (or other MCP client you want to test with).
+3. (Cleanup) run `npm unlink` from repository root.
+
+```json
+{
+  "mcpServers": {
+    "notion-local-package": {
+      "command": "notion-mcp-server",
+      "env": {
+        "NOTION_TOKEN": "ntn_..."
+      }
+    }
+  }
+}
+```
+
+#### Publish
+
+```bash
+npm login
+npm publish --access public
+```

package/docker-compose.yml

@@ -0,0 +1,6 @@
+services:
+  notion-mcp-server:
+    build: .
+    stdin_open: true
+    tty: true
+    restart: unless-stopped

package/package.json

@@ -0,0 +1,63 @@
+{
+  "name": "@mieubrisse/notion-mcp-server",
+  "keywords": [
+    "notion",
+    "api",
+    "mcp",
+    "server"
+  ],
+  "version": "2.0.0",
+  "license": "MIT",
+  "type": "module",
+  "scripts": {
+    "build": "tsc -build && node scripts/build-cli.js",
+    "dev": "tsx watch scripts/start-server.ts",
+    "test": "NODE_ENV=test vitest run",
+    "test:watch": "NODE_ENV=test vitest",
+    "test:coverage": "NODE_ENV=test vitest run --coverage"
+  },
+  "bin": {
+    "notion-mcp-server": "bin/cli.mjs"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.25.1",
+    "axios": "^1.8.4",
+    "express": "^4.21.2",
+    "form-data": "^4.0.1",
+    "mustache": "^4.2.0",
+    "node-fetch": "^3.3.2",
+    "openapi-client-axios": "^7.5.5",
+    "openapi-schema-validator": "^12.1.3",
+    "openapi-types": "^12.1.3",
+    "which": "^5.0.0",
+    "yargs": "^17.7.2",
+    "zod": "3.24.1"
+  },
+  "devDependencies": {
+    "@anthropic-ai/sdk": "^0.33.1",
+    "@types/express": "^5.0.0",
+    "@types/js-yaml": "^4.0.9",
+    "@types/json-schema": "^7.0.15",
+    "@types/mustache": "^4.2.5",
+    "@types/node": "^20.17.16",
+    "@types/which": "^3.0.4",
+    "@vitest/coverage-v8": "3.1.1",
+    "esbuild": "^0.25.2",
+    "multer": "1.4.5-lts.1",
+    "openai": "^4.91.1",
+    "tsx": "^4.19.3",
+    "typescript": "^5.8.2",
+    "vitest": "^3.1.1"
+  },
+  "description": "A maintained fork of the official Notion MCP server",
+  "main": "index.js",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/mieubrisse/notion-mcp-server.git"
+  },
+  "author": "@notionhq",
+  "bugs": {
+    "url": "https://github.com/mieubrisse/notion-mcp-server/issues"
+  },
+  "homepage": "https://github.com/mieubrisse/notion-mcp-server#readme"
+}

package/scripts/build-cli.js

@@ -0,0 +1,30 @@
+import * as esbuild from 'esbuild';
+import { chmod } from 'fs/promises';
+import { fileURLToPath } from 'url';
+import { dirname, join } from 'path';
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+
+async function build() {
+  await esbuild.build({
+    entryPoints: [join(__dirname, 'start-server.ts')],
+    bundle: true,
+    minify: true,
+    platform: 'node',
+    target: 'node18',
+    format: 'esm',
+    outfile: 'bin/cli.mjs',
+    banner: {
+      js: "#!/usr/bin/env node\nimport { createRequire } from 'module';const require = createRequire(import.meta.url);" // see https://github.com/evanw/esbuild/pull/2067
+    },
+    external: ['util'],
+  });
+
+  // Make the output file executable
+  await chmod('./bin/cli.mjs', 0o755);
+}
+
+build().catch((err) => {
+  console.error(err);
+  process.exit(1);
+});