notion-private-api-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_TOKEN_V2 | Yes | Your Notion session cookie (token_v2) | |
| NOTION_PRIVATE_API_BASE | No | API base URL (default: https://www.notion.so) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pageC | Read a Notion page through the Notion private API. |
| get_blockB | Read a single Notion block through the private API. |
| get_block_childrenB | Read direct child blocks for a page or block through the private API. |
| get_style_documentationA | Return the catalog of supported block types, inline annotations (bold/italic/code/link/color/mention), Markdown-to-Notion mapping and block format hints used by this MCP server. Call this before composing complex pages to know what styles you can produce. |
| markdown_to_blocksB | Convert Markdown into the simplified block JSON format. |
| create_pageB | Create a child page under another page from blocks or Markdown. |
| append_blocksB | Append simplified blocks or Markdown to a page. Inserts at the end by default; pass after_block_id to insert immediately after a specific direct child block. |
| replace_page_contentB | Replace direct child blocks of a page with blocks or Markdown. |
| delete_blocksA | Remove direct child blocks from a page and archive those blocks. |
| update_block_textA | Replace the plain text content of a block (e.g. code block). Inline markdown is NOT parsed — text is stored verbatim. |
| sync_markdown_fileB | Create a new page or replace an existing page from a local Markdown file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct operation: page vs block CRUD, content replacement, style documentation, and markdown conversion. No meaningful overlap exists between any two tools.
Most tools follow a verb_noun pattern (e.g., get_page, delete_blocks). However, markdown_to_blocks deviates by using a descriptor format, breaking the uniform convention.
With 11 tools, the set covers core Notion page and block operations, plus supporting utilities. The count is well-scoped for the private API's capabilities without being excessive.
The set covers basic content creation, reading, and modification, but lacks page metadata updates, page deletion, and search. These gaps may hinder some workflows but core content operations are present.