gemmy-notion-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_TOKEN | Yes | Your Notion integration token | |
| NOTION_PAGE_ID | Yes | The ID of a Notion page or database |
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 | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notion_pagesC | Perform various page operations (create, archive, restore, search, update) |
| notion_blocksC | Perform various block operations (retrieve, update, delete, append children, batch operations) |
| notion_databaseC | Perform various database operations (create, query, update) |
| notion_commentsC | Perform various comment operations (get, add to page, add to discussion) |
| notion_usersC | Perform various user operations (list, get, get bot) |
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 5 tools
Each tool maps to a distinct Notion resource (pages, blocks, databases, comments, users), so an agent can generally choose the right tool by resource. However, each tool bundles multiple operations, creating some internal ambiguity, and page-level versus block-level updates may be confused in edge cases.
All tools use the consistent notion_<resource> prefix, and four of five resources are pluralized uniformly. The singular notion_database is a minor deviation from the otherwise plural resource naming pattern.
Five resource-oriented tools are reasonable for a Notion integration and keep the surface compact. The tradeoff is that several tools are broad multi-operation wrappers rather than focused single-action tools, which makes the count feel slightly under-granular.
The surface covers the major Notion resources and supports key lifecycle operations such as page create/archive/restore/search/update, block append/update/delete, and database create/query/update. Some gaps exist, such as explicit page retrieval or delete for databases/comments, but agents can likely work around them.