Better Notion MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_TOKEN | Yes | Your Notion integration token. Get it from https://www.notion.so/my-integrations → Create integration → Copy token → Share pages with integration |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pagesA | Page CRUD for individual pages and database rows. Actions (required params -> optional):
Use |
| databasesA | Database schema, query, and bulk row operations. Actions (required params -> optional):
Use |
| blocksA | Read and modify block-level content within pages. Actions (required params -> optional):
Use |
| usersA | Get user information. Actions (required params):
|
| workspaceA | Search workspace and get workspace info. Actions (required params -> optional):
|
| commentsA | Manage page comments. Actions (required params -> optional):
|
| content_convertA | Convert between markdown and Notion block JSON. Directions: markdown-to-blocks (input: markdown string), blocks-to-markdown (input: JSON array of Notion blocks or JSON string). Most tools (pages, blocks) handle markdown automatically -- use this only for preview/validation. Supported markdown: headings, lists, to-do, code blocks, blockquotes, dividers, callouts (> [!NOTE]), toggles (), tables, images, bookmarks, embeds, equations ($$), columns (:::columns), [toc], [breadcrumb]. Inline: bold, italic, |
| file_uploadsA | Upload files to Notion. Actions (required params -> optional):
Max 20MB direct, multi-part for larger files. |
| helpA | Get full documentation for a tool. Use when compressed descriptions are insufficient. |
| configA | Manage server configuration and credential state. Actions:
|
| config__open_relayA | Open the relay configuration form for better-notion-mcp in the user browser. Returns the relay URL, whether the browser launched, and the current credential state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Pages Tool Docs | |
| Databases Tool Docs | |
| Blocks Tool Docs | |
| Users Tool Docs | |
| Workspace Tool Docs | |
| Comments Tool Docs | |
| Content Convert Tool Docs | |
| File Uploads Tool Docs |
TDQS
Scored across 11 tools
Tools are organized around distinct resources (pages, databases, blocks, users, etc.), and descriptions cross-reference each other to guide selection. However, some overlap remains between pages content operations and blocks append/update, and between databases row operations and pages CRUD, which could still cause occasional misselection.
All tool names use lowercase snake_case, and most are plural resource nouns (pages, databases, blocks, users, comments). Minor deviations exist: content_convert is action-oriented, while help, config, and workspace are singular or uncountable, but the overall pattern is readable and predictable.
With 10-11 tools, the server groups many related actions under resource-level tools rather than exposing dozens of action-specific tools. This is well-scoped for a Notion API surface and each tool clearly earns its place.
The surface covers core Notion workflows: page CRUD, move/archive/restore/duplicate, database schema/query/bulk rows, block-level content CRUD, users, workspace search, comments, and file uploads. Content conversion and configuration/help round out the set, leaving no obvious dead ends for typical agent tasks.