mcp-notion-server

mcp
Guvenlik Denetimi
Gecti
Health Gecti
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 884 GitHub stars
Code Gecti
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested
Purpose
This is a Model Context Protocol (MCP) server that acts as a bridge between Notion and AI agents. It allows compatible AI clients to search, read, query, and update your Notion workspaces directly.

Security Assessment
Overall risk: Medium. The server accesses highly sensitive data because it requires a Notion API token to read and modify your private workspace content. While it routinely makes external network requests to the Notion API, a code scan confirmed no hardcoded secrets, no dangerous permission requests, and no malicious shell command execution. The primary risk is standard for API connectors: an AI agent using this tool could potentially read sensitive notes or delete/modify critical workspace data if not properly instructed.

Quality Assessment
The project is in excellent health and demonstrates strong community trust, evidenced by nearly 900 GitHub stars. It is actively maintained, with recent repository pushes, and is protected by a standard MIT license. A light code audit of 12 files found clean code with no dangerous patterns, indicating a reliable and well-managed codebase.

Verdict
Safe to use, but you should configure your Notion integration capabilities carefully to limit the tool to read-only access unless writing is strictly necessary.
SUMMARY

A Model Context Protocol server for connecting Notion to MCP-compatible clients

README.md

Notion MCP Server

AI-friendly MCP server for the Notion API. It helps agents find, read, query, and update Notion workspaces while keeping responses compact enough for day-to-day AI workflows.

This server targets the Notion API 2026-03-11 and uses the current database/data source model. It exposes MCP tools, prompts, resources, structured tool results, and optional MCP Apps for interactive Notion workflows.

Highlights

  • Search and target discovery with notion_find.
  • Compact page reading with stable block IDs via notion_read_page.
  • Data source schema inspection with notion_inspect_data_source.
  • Schema-aware data source querying and item creation with simple values.
  • Simple page editing tools for paragraphs, headings, lists, todos, quotes, callouts, code blocks, dividers, and safe Markdown append.
  • Raw Notion API tools for advanced block, page, database, data source, comment, and user operations.
  • Optional MCP Apps: Data Source Explorer and Page Workbench.

Quick Start

Add this server to an MCP host such as Claude Desktop:

{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": ["-y", "@suekou/mcp-notion-server"],
      "env": {
        "NOTION_API_TOKEN": "your-integration-token"
      }
    }
  }
}

Restart your MCP host after saving the configuration.

Setup Guide

1. Create a Notion integration

Open the Notion integrations dashboard, then create a new internal integration.

Internal connections
New connections

2. Configure capabilities

Grant only the capabilities you need:

  • Read content: required for search, page reads, data source retrieval, and queries.
  • Insert content: required for creating pages/items and appending blocks.
  • Update content: required for updating pages, blocks, and data source schemas.
  • Read comments / Insert comments: required only for comment tools.
  • User information: required only when using user lookup tools.

For full functionality during setup, enable read, insert, and update content. Add comment or user capabilities only if you plan to use those tools.

Notion integration capabilities

3. Grant content access

Open the Content access tab for your integration, then select the pages or databases you want the MCP server to read or edit.

You can also grant access from the target Notion page or database: open the ... menu, choose Connections, then add your integration.

Notion only lets an integration access pages and databases that have been shared with it. A connection added to a page can also access that page's children.

Edit integration content access

4. Copy the internal integration token

Copy the integration secret. This value becomes NOTION_API_TOKEN in your MCP host config.

Copy internal integration token

5. Configure your MCP host

For Cursor, Claude Desktop, and other MCP hosts, add this server config to your MCP settings:

{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": ["-y", "@suekou/mcp-notion-server"],
      "env": {
        "NOTION_API_TOKEN": "secret_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

For a locally built checkout:

{
  "mcpServers": {
    "notion": {
      "command": "node",
      "args": ["/absolute/path/to/suekou-mcp-notion-server/build/index.js"],
      "env": {
        "NOTION_API_TOKEN": "secret_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Recommended Workflow

  1. Use notion_find to locate a page or data source.
  2. Use notion_read_page for page context and editable block IDs.
  3. Use notion_inspect_data_source before querying or creating data source items.
  4. Use notion_query_data_source_by_values and notion_create_data_source_item_from_values for common data source work.
  5. Use notion_append_markdown, notion_append_content, notion_update_content, or notion_update_content_batch for normal page edits.
  6. Fall back to raw JSON tools only when the simplified tools do not cover the Notion API shape you need.

For Developers

These references are mainly for development, customization, and advanced MCP workflows:

  • Configuration: environment variables, command-line arguments, MCP host examples, development commands, and troubleshooting.
  • Tools: complete tool reference grouped by workflow area.
  • Workflows: practical read, write, data source, migration, and error-handling guidance.
  • MCP Apps: interactive Data Source Explorer and Page Workbench details.

Development

This project uses Node.js 22 or newer and pnpm.

pnpm install --frozen-lockfile
pnpm run build
pnpm test

Use the MCP inspector during local development:

pnpm run inspector

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Yorumlar (0)

Sonuc bulunamadi