Skip to main content
Glama
ai-aviate

better-mcp-notion

by ai-aviate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to better-mcp-notion

No user-submitted related servers found.

    Related Servers

    • notion-mcp-server

      uyencruz
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude, Cursor and ChatGPT to read and write in Notion using a single token, covering search, page creation and editing, database queries, comments and file uploads through natural language. It also supports headless use in automation and CI, with batched, idempotent writes and compact context cost.
      4,756 npm
      MIT

    • notion-mcp-server

      kohaku4865
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives MCP clients like Claude, Cursor, VS Code and Codex token-authenticated read/write access to Notion, so agents can search, create and edit pages, query databases, comment and upload files in plain language. It supports batched, idempotent writes with rollback, markdown round-tripping, and headless use in CI or self-hosted environments.
      4,756 npm
      MIT

    • Notion MCP Server

      mikhail0174
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents and MCP clients token-authenticated read/write access to a Notion workspace, letting them search, create and edit pages, query databases, comment, and upload files in plain language. Writes are batched with atomic rollback and idempotency keys, pages round-trip as markdown, and it runs headless in CI or cron jobs.
      4,756 npm
      MIT

    • notion-mcp-server

      AnneQureshi935
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP clients such as Claude, Cursor, VS Code and Codex to Notion with a single token so agents can search, create and edit pages, query databases, manage blocks and comments, and upload or read files in plain language. Designed for unattended agents and CI, it offers batched idempotent writes, markdown round-tripping, rate-limit retries and low context cost.
      4,756 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources