Manages a simple Notion todo database through Claude with tools for adding, viewing, and completing tasks.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Notion MCP.
danhilse/notion_mcp MCP server provides a small MCP interface for a Notion-based personal todo list. It is designed around a database with three properties: a Task title, a When select field containing only “today” and “later,” and a Checkbox completion field.
The project is intentionally narrow in scope. It is suitable for users who want Claude to work with this specific style of Notion task database, or for developers looking for a starting point for a custom Notion MCP integration. It does not present itself as a general-purpose Notion database connector.
The server uses Notion’s API to read and update the configured database. Claude Desktop starts the MCP process using Python, and the process waits for MCP requests. The Notion integration must have access to the target database before the server can read or modify tasks.
A typical interaction can list every todo, show tasks scheduled for today, create a task with either supported timing value, or update a task’s checkbox to mark it complete. The README describes example requests such as adding an item for today or adding one for later.
Python 3.10 or newer, a Notion account, a Notion integration, and a compatible Notion database are required. Create an integration in Notion, copy its API key, and share the todo database with that integration through the database’s connections settings.
Configuration is supplied through a .env file containing:
NOTION_API_KEY: the Notion integration API key.NOTION_DATABASE_ID: the database identifier used by the server.The documented local setup creates a Python virtual environment and installs the project in editable mode with uv pip install -e .. Claude Desktop can then be configured to run python -m notion_mcp from the project’s virtual environment, with the repository as its working directory. The same module can also be started manually from the project directory when the virtual environment is active.
The danhilse/notion_mcp MCP server supports four task-oriented operations:
These operations map to the fixed database structure rather than exposing arbitrary Notion pages, properties, or database queries. Scheduling is limited to the two values supported by the example schema: “today” and “later.”
The danhilse/notion_mcp MCP server is a personal project with basic error handling and a specific database model. It does not support complex schemas, additional properties, custom fields, recurring tasks, priorities, or tags. A different Notion database structure will likely require edits to server.py, including task creation, task formatting, and possibly the MCP input schema.
The repository documents Claude Desktop as its supported client context. The Notion database must be shared with the integration, and the configured API key and database ID must be available to the running process. The project is released under the MIT License.
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/danhilse-notion-mcp)<a href="https://allmcps.com/mcp/danhilse-notion-mcp"><img src="https://allmcps.com/api/badge/danhilse-notion-mcp?style=directory" alt="Notion MCP on AllMCPs" /></a>