Summary
A focused, read-only Notion reader that keeps an assistant fast and inside its tool limit.
Trimming the tool set and adding parallel block fetching addresses the real friction of Notion in an AI client — too many tools and too many round-trips — so API-get-one-pager can pull an entire page in one recursive call instead of dozens of separate reads.
What it is
A server that gives an assistant read-only access to Notion, deliberately exposing a small set of retrieval tools rather than the full API, so an AI client stays within its tool budget while still reading pages, blocks, databases, and comments.
What you get
- API-retrieve-a-page and API-get-block-children fetch a page and its content blocks, with parallel processing for speed
- API-retrieve-a-block, API-retrieve-a-database, API-retrieve-a-comment, and API-retrieve-a-page-property fetch individual blocks, databases, comments, and page properties
- API-get-one-pager recursively retrieves a full page with all its blocks, databases, and related content in a single call
- API-get-background-result returns the result of a background processing request
Requirements
A Notion integration token, supplied in the client configuration; runs through npx on Node. A read-content-only integration keeps its access to reading.
Setup effort
One command — npx -y notion-readonly-mcp-server