Skip to main content
Glama
makenotion
by makenotion

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AUTH_TOKENNoCustom authentication token for Streamable HTTP transport
NOTION_TOKENNoYour Notion integration token
OPENAPI_MCP_HEADERSNoJSON string containing Authorization header with Bearer token and Notion-Version header (for advanced use cases)

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

NameDescription
API-get-userC

Notion | Retrieve a user

API-get-usersC

Notion | List all users

API-get-selfB

Notion | Retrieve your token's bot user

API-post-database-queryC

Notion | Query a database

API-post-searchC

Notion | Search by title

API-get-block-childrenC

Notion | Retrieve block children

API-patch-block-childrenC

Notion | Append block children

API-retrieve-a-blockC

Notion | Retrieve a block

API-update-a-blockC

Notion | Update a block

API-delete-a-blockC

Notion | Delete a block

API-retrieve-a-pageC

Notion | Retrieve a page

API-patch-pageC

Notion | Update page properties

API-post-pageC

Notion | Create a page

API-create-a-databaseC

Notion | Create a database

API-update-a-databaseC

Notion | Update a database

API-retrieve-a-databaseC

Notion | Retrieve a database

API-retrieve-a-page-propertyC

Notion | Retrieve a page property item

API-retrieve-a-commentC

Notion | Retrieve comments

API-create-a-commentC

Notion | Create comment

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 19 tools

Disambiguation4/5

Most tools have distinct purposes targeting specific Notion resources and actions, with clear separation between operations like create, retrieve, update, and delete. However, some potential overlap exists between 'API-retrieve-a-block' and 'API-get-block-children', as both involve block retrieval but with different scopes, which could cause minor confusion.

Naming Consistency5/5

Tool names follow a highly consistent pattern throughout, using a structured 'API-verb-a-resource' format with hyphens separating components. All tools maintain this convention, making them predictable and easy to parse, with no deviations in style or structure.

Tool Count4/5

With 19 tools, the count is slightly high but reasonable for a comprehensive Notion API server, covering a wide range of operations. It might feel a bit heavy, but each tool appears to serve a specific function in the Notion domain, justifying its inclusion without being excessive.

Completeness5/5

The tool set provides excellent coverage of the Notion API domain, including full CRUD operations for key resources like pages, databases, blocks, and comments, along with search, query, and user management. No obvious gaps are present, enabling agents to handle complete workflows without dead ends.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive