notion-readonly-mcp-server

Notion Readonly MCP Server

Notion ReadOnly MCP Server gives AI assistants retrieval-only access to Notion pages, blocks, databases, comments, and properties. It serves Claude and Cursor users analyzing workspace content, with recursive page exploration and background-result retrieval.

Server facts

notion-readonly-mcp-server

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
4
Last commit
Data as of

Overview

Notion document analysis can involve page metadata, nested blocks, database structure, comments, and individual properties. This project exposes retrieval tools for those parts of a workspace, alongside API-get-one-pager for gathering a page and its related content recursively. Callers can adjust traversal depth and choose whether databases, comments, and detailed properties are included. A separate tool retrieves results from background processing requests. The interface stays focused on reading content rather than modifying Notion data.

For larger page structures, the implementation uses concurrent requests, automatically handles pagination when retrieving child blocks, and caches retrieved content to avoid redundant requests. Setup examples cover npm and Docker configurations for Claude Desktop and Cursor, using a Notion integration secret. Pages and databases must be connected to that integration before they can be accessed. The documentation also distinguishes a read-only tool interface from the broader risks of exposing workspace information to language models, and describes restricting the integration itself to read-content permissions. The server uses the Node runtime, communicates over stdio, and carries an MIT license.

notion-readonly-mcp-server setup notes

  • notion-readonly-mcp-server records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers