No user-submitted related servers found.
Scored across 3 tools
The three tools split cleanly along read/write/introspect lines, so an agent can almost always pick the right tool from intent alone. The only friction is that dozens of operations are multiplexed behind each tool, and the read/write boundary for a few operations (e.g. markdown updates vs. reads) is only resolved by calling notion_describe or by hitting an error.
All three tools follow an identical notion_<verb> pattern (read, write, describe) with the same server prefix. No mixing of casing or verb styles anywhere in the surface.
Three facade tools over a very large Notion operation space is an efficient, well-scoped design rather than a thin one — each tool earns its place and the describe tool exists specifically to offset the small count. It sits just below ideal because discoverability of the underlying operation set is pushed onto the agent rather than exposed structurally.
The surface covers the core Notion lifecycle: search, page/block/database reads, markdown export, plus create/append/update/archive writes with batching and idempotency. The notable gap is that there is no operation-listing tool — agents must already know or guess operation names, with only a few 'common' examples given in the descriptions.