better-mcp-notion
Related Servers
Alternatives to better-mcp-notion
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables natural language interaction with Notion workspace, including search, page/database management, markdown conversion, and productivity shortcuts.27MIT
- FlicenseCqualityCmaintenanceProvides full CRUD capabilities over Notion pages, databases, and content blocks, enabling natural language search, creation, and modification of Notion data.7-
- AlicenseAqualityAmaintenanceEnables precise, schema-validated editing of Notion pages, databases, blocks, properties, and schemas, with dry-run previews, bulk updates, undoable writes, and scheduled automations.33MIT
- FlicenseAqualityDmaintenanceEnables interaction with Notion databases through the Notion API, supporting full CRUD operations on pages and databases. Supports advanced querying, filtering, sorting, and all property types with Docker deployment for easy integration with Cursor and Claude.8-
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to search, query, create, and update content in connected workspaces through the Notion API, including data source operations and Markdown-based page reading and editing.195,447 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Notion databases and pages via the Notion API. Allows searching, reading, and writing to Notion through natural language.-
TDQS
Scored across 9 tools
Most tools have clearly distinct roles: read, delete, search, list, move, schema, and comment are well-separated. The main ambiguity is between write and update, since write can also update properties and content, while update is explicitly scoped to property-only changes. The descriptions help clarify the boundary, but an agent could still hesitate when deciding which to use for a property update.
All tool names are single lowercase words used as imperative commands, which creates a strong, predictable pattern. Write, read, search, list, delete, move, update, schema, and comment are all short and consistent in style. Minor semantic quibbles like 'schema' being a noun do not break the overall consistency.
Nine tools is a well-scoped size for a Notion MCP server. Each tool covers a meaningful area of Notion interaction without excessive fragmentation or redundancy. The set feels appropriately balanced for both simple and moderately complex workflows.
The server covers the core page lifecycle well: create/update via write, property-only updates, read, search, list, move, delete, schema management, and comments. Minor gaps exist, such as no way to create a brand-new database from scratch, no unarchive/restore operation, and no granular block-level editing. These are workable limitations rather than critical dead ends.