Notion MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port number for HTTP transport | 3003 |
| NOTION_API_KEY | Yes | Your Notion integration token | |
| NOTION_VERSION | No | The Notion API version | 2022-06-28 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notion_create_pageB | Creates a new page in Notion. Can be a child of a page or database. |
| notion_retrieve_pageA | Retrieves a Notion page by ID. Returns page properties, not page content. |
| notion_update_pageC | Updates properties of a Notion page. Can also update icon, cover, or archive/restore pages. |
| notion_retrieve_page_propertyB | Retrieves a specific property of a Notion page. Use for properties with more than 25 references. |
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 4 tools
The tools are mostly distinct, with each handling a specific aspect of page management (create, retrieve, update). However, 'notion_retrieve_page' and 'notion_retrieve_page_property' could cause confusion, as the latter is a specialized case of the former, potentially leading to misselection when an agent needs general page info versus a specific property.
All tool names follow a consistent 'notion_verb_noun' pattern using snake_case, with clear verbs like create, retrieve, and update. This predictability makes it easy for agents to understand and use the toolset without naming conflicts or style mismatches.
With 4 tools, the count is borderline for a Notion integration, as it covers basic CRUD operations but feels thin. A typical Notion server might include additional tools for databases, blocks, or search to provide more comprehensive coverage, making this set somewhat limited in scope.
The toolset covers create, retrieve, and update operations for pages, but has notable gaps. There is no delete tool, and it lacks support for databases, blocks, or search functionalities, which are core to Notion's domain. This incompleteness may require agents to work around missing operations for full lifecycle management.