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:
|
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 10 tools
Tools are largely separated by Notion resource (pages, blocks, databases, comments, users, workspace), so most selections are clear. There is some overlap between pages.update/append_content and blocks.append, and between databases row operations and pages CRUD, though the descriptions provide guidance.
The dominant pattern is resource-noun tools with action subcommands, which is predictable and readable. Minor deviations include singular config/workspace, plural file_uploads/users/pages, and utility names like help and content_convert.
At 10 tools, the server is well-scoped for the Notion API surface. Each tool groups a meaningful resource area without forcing an excessive number of separate tools.
The surface covers the main Notion workflows: pages, blocks, databases, comments, users, workspace search, file uploads, and content conversion. Minor gaps or unclear areas remain around database-level archive/delete and block reordering/moving.