Skip to main content
Glama
kerwin77106

notion-multi-mcp

by kerwin77106

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NOTION_ACCOUNTSYesComma-separated list of prefix:api_key pairs, e.g. work:ntn_key1,personal:ntn_key2

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
default_searchC

[default] Search pages and databases

default_query_databaseB

[default] Query database contents (use data_source_id, not database_id)

default_create_pageD

[default] Create a new page

default_retrieve_pageC

[default] Get page information

default_update_pageC

[default] Update page properties

default_retrieve_page_propertyC

[default] Get a specific page property

default_move_pageC

[default] Move a page to a new parent

default_retrieve_blockC

[default] Get block information

default_update_blockC

[default] Update a block

default_delete_blockC

[default] Delete a block

default_get_block_childrenC

[default] List child blocks

default_append_block_childrenC

[default] Append child blocks

default_retrieve_databaseC

[default] Get database schema

default_create_databaseC

[default] Create a new database

default_update_databaseC

[default] Update database properties

default_query_data_sourceC

[default] Query a data source

default_retrieve_data_sourceC

[default] Get data source info

default_list_data_source_templatesC

[default] List data source templates

default_update_data_sourceD

[default] Update a data source

default_create_commentC

[default] Create a comment

default_retrieve_commentsD

[default] List comments

default_get_selfA

[default] Get bot user info

test_searchC

[test] Search pages and databases

test_query_databaseC

[test] Query database contents (use data_source_id, not database_id)

test_create_pageD

[test] Create a new page

test_retrieve_pageC

[test] Get page information

test_update_pageC

[test] Update page properties

test_retrieve_page_propertyC

[test] Get a specific page property

test_move_pageC

[test] Move a page to a new parent

test_retrieve_blockC

[test] Get block information

test_update_blockD

[test] Update a block

test_delete_blockC

[test] Delete a block

test_get_block_childrenC

[test] List child blocks

test_append_block_childrenD

[test] Append child blocks

test_retrieve_databaseC

[test] Get database schema

test_create_databaseC

[test] Create a new database

test_update_databaseC

[test] Update database properties

test_query_data_sourceD

[test] Query a data source

test_retrieve_data_sourceC

[test] Get data source info

test_list_data_source_templatesC

[test] List data source templates

test_update_data_sourceD

[test] Update a data source

test_create_commentC

[test] Create a comment

test_retrieve_commentsC

[test] List comments

test_get_selfB

[test] Get bot user info

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2/5.0

Scored across 44 tools

Disambiguation2/5

The tools are duplicated with `default_` and `test_` prefixes, creating two identical sets. An agent cannot easily distinguish which set to use, leading to potential misselection. Within each set, tools are distinct, but the overlap across sets causes ambiguity.

Naming Consistency2/5

The naming pattern is mostly verb_noun but the prefix system is inconsistent: `default_` vs `test_` for the same operations. Additionally, there is a mix of `get` and `retrieve` verbs (e.g., `get_block_children` vs `retrieve_block`), breaking consistency.

Tool Count2/5

With 44 tools, the count is too high for the server's purpose. The duplication of 22 tools for default and test environments inflates the count unnecessarily. A single set of ~22 tools would be more appropriate.

Completeness3/5

The tool surface covers many Notion operations (blocks, pages, databases, comments, data sources), but some gaps exist: no delete for pages or databases, no update for comments. The coverage is decent but not fully complete.

Maintenance

ActivityNo data
ResponsivenessNo issues