Loading...

A Model Context Protocol (MCP) server that connects to Notion, enabling management of tasks and to-do lists within a Notion workspace.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
A Model Context Protocol (MCP) server that connects to Notion, enabling management of tasks and to-do lists within a Notion workspace.
This MCP server is relatively safe for managing tasks within a defined Notion page. However, the risk lies in mishandling the Notion API token and potential unintended modifications to the Notion database if the tool functions are misused or improperly configured.
Performance depends on the Notion API's responsiveness and the size of the Notion database. Large databases may result in slower query times.
Cost is primarily related to Notion API usage. Monitor API call volume to avoid exceeding rate limits or incurring unexpected charges.
npx -y @smithery/cli install @Badhansen/notion-mcp --client claude{
"mcpServers": {
"notion-mcp": {
"command": "uv",
"args": [
"--directory",
"/Users/username/Projects/Python/notion-mcp/src" /* Path to your project */,
"run",
"server.py"
]
}
}
}NOTION_TOKENNOTION_BASE_URLshow_all_todosRetrieves and displays all tasks from the configured Notion workspace.
Read-only operation; no modifications are made to the Notion database.
add_todoAdds a new task to the Notion workspace with the provided task description.
Adds data to the Notion database, but does not modify existing entries in a destructive way.
complete_todoUpdates an existing task in the Notion workspace to mark it as complete.
Modifies existing data in the Notion database, but does not delete any data.
API Key
cloud
This MCP server is relatively safe for managing tasks within a defined Notion page. However, the risk lies in mishandling the Notion API token and potential unintended modifications to the Notion database if the tool functions are misused or improperly configured.
The MCP server has read and write access to the Notion database, so it can automatically add, update, and retrieve tasks. There is no built-in sandboxing or rollback support.
Production Tip
Secure the `.env` file containing the Notion API token and regularly review the task modifications made by the MCP server.
Create a new integration in your Notion workspace at notion.so/my-integrations and copy the API key.
Open your Notion page, click the '...' menu, select 'Add connections', and search for your integration by name.
Store the token in a `.env` file as `NOTION_TOKEN`.
The MCP server may return errors, and you may need to implement retry logic or reduce the frequency of API calls.
No, the server is configured to work with a single Notion workspace specified by the `PAGE_ID`.
Fork the repository, create a feature branch, and submit a pull request with your changes.
While it uses API keys, ensure your `.env` file is protected and be mindful of the write access it grants to your Notion database.