Notion MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_API_KEY | Yes | Your Notion integration API key |
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 |
|---|---|
| searchD | – |
| query-databaseD | – |
| get-databaseD | – |
| create-pageD | – |
| get-pageD | – |
| update-pageD | – |
| append-blocksD | – |
| get-blockD | – |
| get-block-childrenD | – |
| update-blockD | – |
| delete-blockD | – |
| list-usersD | – |
| get-userD | – |
| get-meD | – |
| create-commentD | – |
| list-commentsD | – |
| create-link-previewD | – |
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 17 tools
Each tool has a clearly distinct purpose targeting specific Notion resources and actions. For example, get-block vs get-block-children vs update-block are clearly differentiated, and there's no overlap between operations like create-page, update-page, and get-page.
All tools follow a consistent verb-noun pattern with kebab-case naming throughout (e.g., create-page, get-block, query-database). The naming convention is perfectly uniform across all 17 tools.
17 tools is slightly high but reasonable for a comprehensive Notion API integration. It covers multiple resource types (pages, blocks, databases, users, comments) with appropriate operations, though it might feel slightly heavy compared to more minimal implementations.
The tool set provides excellent coverage of Notion's core functionality including CRUD operations for pages, blocks, and comments, plus database querying, user management, and search. Minor gaps might include missing operations like deleting pages or databases, but agents can work around these limitations.