notion-mcp
Related Servers
Alternatives to notion-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for the Notion API, enabling management of pages, blocks, databases, data sources, comments, and users through natural language.4 npm3MIT
- AlicenseBqualityBmaintenanceA lightweight MCP server for Notion that enables natural language management of pages, databases, and blocks through the current Notion API.12MIT
- -licenseNot gradedqualityNot gradedmaintenanceAn MCP server that enables natural language interaction with the Notion API, allowing users to search, comment, create pages, and access content within their Notion workspace.122,532 npm-
- AlicenseAqualityCmaintenanceAn MCP server for Notion API with optimized token efficiency and full database property filtering, enabling AI assistants to manage pages, databases, and blocks.3210 npm1MIT
- AlicenseNot gradedqualityDmaintenanceComprehensive MCP server for the Notion API. Provides 22 tools for full CRUD operations on pages, databases, blocks, users, and comments.10 npmMIT
- AlicenseCqualityDmaintenanceAn MCP server that converts Markdown content to Notion API-compatible formats, suitable for content management and development integration.11Apache 2.0
TDQS
Scored across 44 tools
Most tools target a distinct Notion resource/action, but a few close pairs (e.g., notion_read_page vs notion_read_page_markdown, notion_update_page vs notion_update_page_content vs notion_replace_page_content) could cause misselection without careful reading of descriptions. Overall, descriptions are detailed enough to disambiguate, so the overlap is manageable.
All tools share the 'notion_' prefix and generally follow verb_noun naming, but the verbs are inconsistent across similar actions (add vs upload, get vs read/list/query, update vs replace/append). This inconsistency creates some friction, though the pattern is still predictable overall.
44 tools is far beyond the typical well-scoped range and feels heavy for a single server, even for a broad API like Notion. Several tools could be consolidated (e.g., three ways to modify page content, multiple file-purge variants), and the sheer number increases cognitive load and misselection risk.
The tool set provides thorough coverage of Notion's core surface: CRUD for pages, databases, blocks, comments, views, and users, plus rich file operations (upload, download, replace, extract, render, batch attach). There are few obvious gaps—the domain appears fully supported for common workflows.