Notion MCP Integration

Name: Notion MCP Integration
Author: danhilse

@danhilse

リポジトリホームページ

Notion MCP Integration について

A simple MCP integration that allows Claude to read and manage a personal Notion todo list

#notion #claude #mcp-servers

基本情報

カテゴリ

メモリとナレッジ

ライセンス

MIT

ランタイム

python

トランスポート

stdio

公開者

danhilse

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "notion_mcp": {
      "command": "python",
      "args": [
        "-m",
        "venv",
        ".venv"
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Notion MCP Integration?

A simple Model Context Protocol (MCP) server that integrates with Notion’s API to manage a personal todo list through Claude. It is tailored for a specific Notion database structure with three properties: Task (title), When (select with only “today” or “later”), and Checkbox (marks completion). This is a personal project intended for a minimalist todo list setup.

How to use Notion MCP Integration?

Clone the repository, set up a Python 3.10+ virtual environment, install dependencies with uv pip install -e ., create a Notion integration and obtain an API key, share your Notion database with that integration, and place the API key and database ID in a .env file. Configure Claude Desktop by adding the server to claude_desktop_config.json with the command pointing to the project’s virtual environment. Run the server automatically through Claude Desktop (recommended) or manually via python -m notion_mcp. Use natural language commands like “Show all my todos”, “What’s on my list for today?”, “Add a todo for today: check emails”, or “Add a task for later: review project”.

Key features of Notion MCP Integration

Add new todo items to Notion
View all todos from the database
View only today’s tasks
Check off a task as complete

Use cases of Notion MCP Integration

Manage a personal todo list through Claude chat
Quickly capture tasks with a “today” or “later” schedule
Get a daily overview of tasks marked for today
Mark tasks as done without opening Notion

FAQ from Notion MCP Integration

What database structure does Notion MCP Integration require?

It expects a Notion database with exactly three properties: a title property named “Task”, a select property named “When” with only two options “today” and “later”, and a checkbox property named “Checkbox”. The code is not designed for more complex schemas.

Can I customize Notion MCP Integration for my own database structure?

Yes, you can modify the server.py file – particularly the create_todo() function, the todo formatting in call_tool(), and the input schema in list_tools() – to match different property names, types, or options.

What are the prerequisites to use Notion MCP Integration?

Python 3.10 or higher, a Notion account, a Notion integration (API key) created at https://www.notion.so/my-integrations, and a Notion database that matches the required structure (or willingness to modify the code).

What limitations does Notion MCP Integration have?

It only works with the specific database structure described. It has no support for complex schemas, additional properties, recurring tasks, priorities, tags, or advanced error handling. Task scheduling is limited to “today” or “later”.

How do I run Notion MCP Integration?

You can run it directly from the command line with python -m notion_mcp after activating the virtual environment, or configure it in Claude Desktop’s claude_desktop_config.json so it starts automatically when Claude launches and stops when Claude is closed.

「メモリとナレッジ」の他のコンテンツ

Context Portal MCP (ConPort)

GreatScottyMac

Context Portal (ConPort): A memory bank MCP server building a project-specific knowledge graph to supercharge AI assistants. Enables powerful Retrieval Augmented Generation (RAG) for context-aware development in your IDE.

763

Notion MCP Server

awkoy

Notion MCP server for Claude, Cursor, ChatGPT & Claude Desktop. Connect AI agents to Notion via Model Context Protocol — pages, databases, blocks, comments, files.

159