notion-multi-mcp
Related Servers
Alternatives to notion-multi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that provides AI assistants with full access to Notion workspaces, enabling search, read, create, and update pages, databases, and blocks.132 npmMIT

Notion MCP Serverofficial
AlicenseBqualityCmaintenanceAn MCP server that enables AI assistants to interact with the Notion API, allowing them to search, read, comment on, and create content in Notion workspaces through natural language commands.19128,047 npm4,641MIT- AlicenseAqualityAmaintenanceNotion MCP Server is a MCP server implementation that enables AI assistants to interact with Notion's API.32,184 npm171MIT
- AlicenseAqualityCmaintenanceAn MCP server for Notion API with optimized token efficiency and full database property filtering, enabling AI assistants to manage pages, databases, and blocks.3224 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that connects AI assistants to Notion, enabling automated research, GitHub tracking, and content pipelines with human-in-the-loop approval via a Notion task queue.59MIT
- AlicenseAqualityDmaintenanceA high-performance MCP server that integrates Notion into AI workflows, enabling interaction with Notion pages, databases, and comments through a standardized protocol.841 npm27Apache 2.0
TDQS
Scored across 44 tools
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.
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.
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.
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.