notion-mcp

MCP.Pizza Chef: ccabanillas

Seven tools cover the basics: list your databases, look inside one, query its rows, search everything, read a page's contents, create a page and update one. Two practical catches are worth knowing. The sample configuration in the README uses the wrong key name for Claude Desktop, so copying it as-is silently does nothing. And the update tool has an archived option that sends a page to Notion's trash with no confirmation step. The project has had no changes since June 2025.

Unmaintained · No commits in 13 months.
Data
Notes
Writing

Use This MCP server To

Find a note in my Notion workspace without opening the app Add a new row to my tasks database from chat Update the status on a project page I am tracking Pull this week's items out of a Notion database Read a long Notion page and summarise it for me

README

Notion MCP Server

smithery badge

A Model Context Protocol (MCP) server implementation for Notion integration, providing a standardized interface for interacting with Notion's API. Compatible with Claude Desktop and other MCP clients.

Features

  • List and query Notion databases
  • Create and update pages
  • Search across Notion workspace
  • Get database details and block children
  • Full async/await support with httpx
  • Type-safe with Pydantic v2 models
  • Proper error handling with detailed logging
  • Compatibility with MCP 1.6.0

Installation

Installing via Smithery

To install Notion Integration Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @ccabanillas/notion-mcp --client claude

Manual Installation

  1. Clone the repository:
git clone https://github.com/ccabanillas/notion-mcp.git
cd notion-mcp
  1. Create a virtual environment and install dependencies (using uv):
uv venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate
uv pip install -e .

Alternatively, using standard venv:

python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate
pip install -e .
  1. Create a .env file in the project root:
NOTION_API_KEY=your_notion_integration_token

Usage

  1. Test the server (it should run without errors):
python -m notion_mcp
  1. To use it with Claude Desktop, adjust your claude_desktop_config.json file (located at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
  "servers": {
    "notion-mcp": {
      "command": "/Users/username/Projects/notion-mcp/.venv/bin/python",
      "args": ["-m", "notion_mcp"],
      "cwd": "/Users/username/Projects/notion-mcp"
    }
  }
}

Be sure to replace /Users/username/ with your actual home directory path.

Development

Project Structure

notion-mcp/
├── src/
│   └── notion_mcp/
│       ├── models/
│       │   ├── __init__.py
│       │   └── notion.py      # Pydantic models for Notion objects
│       ├── __init__.py        
│       ├── __main__.py        # Entry point
│       ├── client.py          # Notion API client
│       └── server.py          # MCP server implementation
├── .env                       # Environment variables (add your Notion API key here)
├── .gitignore
├── pyproject.toml             # Project dependencies
└── README.md

Running Tests

pytest

Configuration

The server requires a Notion integration token. To set this up:

  1. Go to https://www.notion.so/my-integrations
  2. Create a new integration with appropriate capabilities (read/write as needed)
  3. Copy the integration token
  4. Add it to your .env file in the project root directory:
NOTION_API_KEY=your_notion_integration_token
  1. Share your Notion databases with the integration (from the database's "Share" menu)

Contributing

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

License

MIT License - Use at your own risk

Troubleshooting

Common Issues

  • Connection Errors: Make sure your Notion API key is correct and you have internet access
  • Permission Errors: Ensure your integration has been given access to the databases you're trying to access
  • Claude Desktop Integration: If Claude Desktop isn't connecting, check that your config path is correct and that the server is running without logging to stdout

Acknowledgments

  • Built to work with Claude Desktop and other MCP clients
  • Uses Notion's API (latest compatible version 2022-02-22)
  • MCP 1.6.0 compatibility maintained
  • Special thanks to danhilse, I referenced his notion-mcp-server project

notion-mcp FAQ

Do I need a key?
Yes, though not your Notion password. You create an internal integration at notion.so/my-integrations and copy its token. The server refuses to start without one.
Why can it not see any of my pages?
A Notion integration sees nothing by default. Open each database or page, use its Share menu, and grant the integration access before expecting results.
The setup snippet in the README does not work. Why?
It uses "servers" as the top-level name. Claude Desktop expects "mcpServers", so change that one word and the connection will appear.
Can it delete my work?
Not outright, but the update tool accepts an archived flag that moves a page to Notion's trash, with no confirmation prompt and no read-only mode to block it. Trashed items can be restored from Notion.
Can I use this to add a task to my Notion database?
Yes — it creates a page in any database the integration has been shared with and fills in the properties you specify.
How hard is setup?
Developer-level. You clone the project, make a Python environment, install it, and add a file holding your token. Smithery offers a one-command alternative if you would rather skip that.
Which apps does it work in?
It is written for Claude Desktop and works in any assistant that can start a local command-line server.
Is it up to date with Notion?
Not really. It is pinned to Notion's 2022 interface version and has had no code changes since June 2025, so newer Notion features are out of reach.