Notion MCP Client

@phoenine

About Notion MCP Client

A simple MCP server that integrates with Notion's API to manage my personal habit track.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "notion-mcp": {
      "command": "uvx",
      "args": [
        "notion-mcp"
      ],
      "env": {
        "NOTION_TOKEN": "",
        "ROOT_PAGE_ID": ""
      }
    }
  }
}

Tools

No tools detected

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Notion MCP Client?

Notion MCP Client is a Model Context Protocol (MCP) client for interacting with the Notion API, designed for use in AI tools like Claude that support MCP. It can also fall back to a standard HTTP API when MCP is not available.

How to use Notion MCP Client?

Install via pip install notion-mcp (or with MCP support: pip install notion-mcp[mcp]). Configure a .env file with your Notion token and root page ID. Run the CLI with notion-mcp or start the server with notion-mcp-server --host 0.0.0.0 --port 8000. You can also supply a JSON configuration file.

Key features of Notion MCP Client

Asynchronous API operations with retry logic
Concurrency control to respect Notion API rate limits
Environment-based and JSON-based configuration
Flexible server implementation with MCP support
Falls back to standard HTTP API when MCP is unavailable
Supports custom operations like fill_web_url

Use cases of Notion MCP Client

Use with Claude to manipulate Notion databases and pages via natural language
Automate filling URL fields across pages in selected databases
Integrate with any web framework using the NotionRequestHandler class
Run as a standalone HTTP server for custom clients

FAQ from Notion MCP Client

What dependencies or runtime are required?

Python 3.x and the packages installed via pip. For MCP support, install with the [mcp] extra.

What API credentials are needed?

A Notion API token (NOTION_TOKEN) and a root page ID (ROOT_PAGE_ID) are required, set via environment variables or a JSON configuration file.

Where does data live?

Data remains in Notion. The client reads and writes to your Notion workspace through the Notion API; no data is stored locally beyond configuration.

What transport protocols are supported?

MCP (Model Context Protocol) when available; otherwise, the server falls back to a standard HTTP API that accepts POST requests at /notion.

Are there any known limits?

The client uses configurable concurrency limits and retry delays (e.g., CONCURRENCY_LIMIT=5, RETRY_DELAYS=1,3,5) to respect Notion API rate limits. Only one operation (fill_web_url) is documented; more are planned.

Frequently asked questions

What dependencies or runtime are required?

Python 3.x and the packages installed via pip. For MCP support, install with the `[mcp]` extra.

What API credentials are needed?

A Notion API token (`NOTION_TOKEN`) and a root page ID (`ROOT_PAGE_ID`) are required, set via environment variables or a JSON configuration file.

Where does data live?

Data remains in Notion. The client reads and writes to your Notion workspace through the Notion API; no data is stored locally beyond configuration.

What transport protocols are supported?

MCP (Model Context Protocol) when available; otherwise, the server falls back to a standard HTTP API that accepts POST requests at `/notion`.

Are there any known limits?

The client uses configurable concurrency limits and retry delays (e.g., `CONCURRENCY_LIMIT=5`, `RETRY_DELAYS=1,3,5`) to respect Notion API rate limits. Only one operation (`fill_web_url`) is documented; more are planned.