MCP Notion Server (@suncreation)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_API_KEY | No | Alternative name for the token (either works) | |
| NOTION_API_TOKEN | No | Your Notion API integration token | |
| NOTION_MARKDOWN_CONVERSION | No | Set to "true" for Markdown output (reduces tokens) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notion_append_block_childrenA | Append children blocks to a parent block. LIMITS: Max 100 blocks, 2 nesting levels, 2000 chars per rich_text/URL. |
| notion_retrieve_blockB | Retrieve a block from Notion |
| notion_retrieve_block_childrenC | Retrieve the children of a block |
| notion_delete_blockC | Delete a block in Notion |
| notion_update_blockA | Update the content of a block in Notion based on its type. The update replaces the entire value for a given field. |
| notion_create_pageA | Create a page as child of page or database. LIMITS: 100 blocks, 2 nesting levels, 2000 chars. |
| notion_retrieve_pageB | Retrieve a page from Notion |
| notion_update_page_propertiesB | Update properties of a page or an item in a Notion database |
| notion_list_all_usersA | List all users in the Notion workspace. Note: This function requires upgrading to the Notion Enterprise plan and using an Organization API key to avoid permission errors. |
| notion_retrieve_userA | Retrieve a specific user by user_id in Notion. Note: This function requires upgrading to the Notion Enterprise plan and using an Organization API key to avoid permission errors. |
| notion_retrieve_bot_userB | Retrieve the bot user associated with the current token in Notion |
| notion_create_databaseC | Create a database in Notion |
| notion_query_databaseC | Query a database in Notion |
| notion_retrieve_databaseB | Retrieve a database in Notion |
| notion_update_databaseC | Update a database in Notion |
| notion_create_database_itemB | Create a new item (page) in a Notion database |
| notion_create_commentA | Create a comment in Notion. This requires the integration to have 'insert comment' capabilities. You can either specify a page parent or a discussion_id, but not both. |
| notion_retrieve_commentsB | Retrieve a list of unresolved comments from a Notion page or block. Requires the integration to have 'read comment' capabilities. |
| notion_searchB | Search pages or databases by title in Notion |
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 19 tools
Most tools have distinct purposes targeting specific Notion resources (blocks, databases, pages, users, comments), but some potential overlap exists between notion_create_page and notion_create_database_item (both create pages, though in different contexts) and between notion_retrieve_block and notion_retrieve_page (both retrieve content, but blocks vs. pages). The descriptions help clarify these distinctions.
All tool names follow a consistent verb_noun pattern with 'notion_' prefix (e.g., notion_create_page, notion_retrieve_database, notion_update_block). The verbs (append, create, delete, list, query, retrieve, search, update) are used predictably across resources, making the set highly readable and systematic.
19 tools is slightly high but reasonable for a Notion server covering blocks, databases, pages, users, and comments. It includes essential CRUD operations and utilities like search and listing, though it might be borderline heavy compared to simpler APIs. Each tool appears to serve a specific function without obvious redundancy.
The tool set provides comprehensive coverage of the Notion domain, including full CRUD for blocks, databases, pages, and comments, plus utilities like search, user management, and querying. There are no apparent gaps; agents can perform complete workflows from creation to deletion and retrieval across all major resource types.