notion-private-api-mcp
Related Servers
Alternatives to notion-private-api-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceFull-featured Notion MCP server enabling deep page reading, block editing, snapshot/restore, file uploads, table manipulation, page restore, and destructive page copying.33MIT
- AlicenseBqualityBmaintenanceA lightweight MCP server for Notion that enables natural language management of pages, databases, and blocks through the current Notion API.12MIT
- AlicenseAqualityCmaintenanceRead-only MCP server that exposes your local Notion backups to AI agents — query databases, read pages, search a backed-up workspace. Offline by default: no LLM calls, no telemetry, no cloud.61MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server that exposes the official Notion SDK, allowing AI models to interact with Notion workspaces.1735 npm10Apache 2.0
- FlicenseNot gradedqualityBmaintenanceRemote MCP server that exposes Notion as tools (search, get, create pages, append blocks, query databases) via Streamable HTTP with bearer auth, designed for deployment on Railway.-
- AlicenseNot gradedqualityDmaintenanceA local MCP server for the Notion API, enabling AI agents to read, write, and manage Notion pages and databases. This fork restores database creation support.127 npmMIT
TDQS
Scored across 11 tools
Each tool targets a distinct operation: page vs block CRUD, content replacement, style documentation, and markdown conversion. No meaningful overlap exists between any two tools.
Most tools follow a verb_noun pattern (e.g., get_page, delete_blocks). However, markdown_to_blocks deviates by using a descriptor format, breaking the uniform convention.
With 11 tools, the set covers core Notion page and block operations, plus supporting utilities. The count is well-scoped for the private API's capabilities without being excessive.
The set covers basic content creation, reading, and modification, but lacks page metadata updates, page deletion, and search. These gaps may hinder some workflows but core content operations are present.