Notion MCP Server is a self-hosted Model Context Protocol server that exposes the Notion API to AI agents and MCP clients such as Cursor, Claude Desktop, Zed, and GitHub Copilot CLI. Agents can search a workspace, read and create pages, comment, and query databases through tools derived from the Notion API, planning multi-step calls from a plain instruction such as commenting on a named page.
Notion now directs users to Remote Notion MCP, its hosted server, and this local implementation is no longer actively maintained. The hosted server adds semantic search across the workspace and connected apps, Markdown-native page editing, and OAuth that respects each user's existing permissions, where this project offers keyword search, API-derived tools, and manual token and page-sharing configuration.
| Feature | Remote Notion MCP | This project |
|---|---|---|
| Hosting | Hosted | Runs and updates locally |
| Search | Semantic, across the workspace and connected apps | Keyword search only |
| Page content | Markdown-native reading and editing | Two Markdown page-content tools |
| Authentication | OAuth, respects existing permissions | Manual integration token and page sharing |
| Support | Active | Not actively supported |
Version 2.0 moved to the Notion API release that makes data sources the primary abstraction for databases, replacing the database query, create, and update tools with data-source equivalents and bringing the total to 22 tools. Access is scoped by the Notion integration the server runs with, so an integration limited to read access yields a read-only server.
Features
- Notion API tools: 22 tools covering search, pages, comments, databases, and data sources, discovered automatically by the client
- Data sources: query, retrieve, create, and update data sources, list data-source templates, and move pages between parents
- Markdown page content: read a page as Markdown, optionally with meeting-note transcripts, and edit it with whole-page replacement or targeted find-and-replace
- Transports: standard input/output for desktop MCP clients, or Streamable HTTP with bearer-token authentication for web-based clients
- Multi-tenant passthrough: one HTTP deployment can serve several Notion integrations, with each client supplying its own token per session
- Scoped access: permissions follow the Notion integration's capabilities and the pages shared with it, so a read-only integration limits the server to reads
- Container image: an official Docker image as an alternative to the npm package
