NotionMCP MCP Server

NotionMCP becomes available to MCP clients through the notionmcp mcp server. MCP server for Notion integration.

What NotionMCP does

A Model Context Protocol (MCP) server that connects Claude and other AI assistants to your Notion workspace. This integration allows AI assistants to interact with your Notion databases, pages, and blocks.

This tool acts as a bridge between AI assistants (like Claude) and your Notion workspace. It allows the AI to: - View and search your Notion databases - Create and update pages - Manage content blocks - And much more!

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• Name — Choose a name like "Claude Assistant" or "AI Helper"
• Logo — Optional
• list-databases — View all accessible databases
• query-database — Get entries from a database
• create-page — Add a new page to a database
• update-page — Modify an existing page
• create-database — Create a new database
• update-database — Modify a database structure
• get-page — View a specific page
• get-block-children — View content blocks
• append-block-children — Add content to a page
• update-block — Edit content blocks
• get-block — View a specific block
• search — Find content across your workspace

Installing the notionmcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: NOTION_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js (version 14 or higher) - A Notion account - Claude Desktop app (if using with Claude)

Where it fits

Database servers turn schema archaeology and ad-hoc reporting into conversation, which is why they tend to be the second or third server people install. NotionMCP sits in that group, and the shape of its toolset — Name, Logo, list-databases among others — tells you what it is really for. Worth comparing against the other databases servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use NotionMCP.
• Maintained by Sjotie, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the notionmcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.