Skip to main content
Glama
Sign In
Easy Notion MCP

Easy Notion MCP

by Grey-Iris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Easy Notion MCP

No user-submitted related servers found.

    Related Servers

    • tiny-notion-mcp

      AyanoT1
      A
      license
      A
      quality
      C
      maintenance
      A lightweight Notion MCP server that minimizes token usage by returning Markdown instead of raw JSON, enabling efficient read/write operations on Notion pages.
      9
      MIT

    • notion-slim

      mcpslim
      A
      license
      Not graded
      quality
      D
      maintenance
      A token-optimized MCP server for Notion that reduces context window usage by 73% while preserving full functionality, enabling AI assistants to interact with Notion efficiently.
      9 npm
      2
      MIT

    • MCP Notion Server

      SunCreation
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables LLMs to interact with Notion workspaces via the Notion API, supporting page creation, database management, and content retrieval. It features markdown conversion to optimize token usage and enhanced error handling for more reliable workspace interactions.
      19
      21 npm
      1
      MIT

    • notion-mcp-server

      sylviel2810
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP-capable AI clients such as Claude, Cursor, VS Code and Codex to Notion with a single token, letting them search, create and edit pages, query databases, comment and upload files in plain language. It supports headless and CI use, batched idempotent writes, markdown round-tripping, and low context overhead.
      4,107 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

    A3.7/5.0

    Scored across 43 tools

    Disambiguation4/5

    Most tools are clearly distinct by resource (page, block, toggle, database, view, comment, user). Some potential confusion exists between update_section/update_toggle/update_block and read_section/read_block/read_toggle, but descriptions clarify the target granularity. The pair add_database_entry/add_database_entries is intentionally similar but the plural is self-explanatory.

    Naming Consistency4/5

    The set predominantly uses verb_noun naming (create_page, read_page, update_page, archive_page, restore_page, query_database, add_database_entry, delete_database_entry). Minor deviations exist: get_view vs list_views, get_database vs list_databases, and get_me/get_config don't follow the verb_noun pattern, but the overall convention is consistent and predictable.

    Tool Count3/5

    43 tools is on the heavy side for a single MCP server, but the breadth roughly matches Notion's feature surface (pages, blocks, toggles, databases, views, comments, users). The count is justified by the domain, though it approaches the upper bound where navigation becomes burdensome.

    Completeness5/5

    The tool surface covers the full lifecycle for pages (create, read, update, archive, restore, duplicate, move), blocks (read, update, delete, append, replace), toggles (read, update, archive, restore), databases (create, get, list, query, update schema, add/update/delete entries), views (list, create, update, delete), comments, and users. Notable gaps like subpage deep-duplication and database inline toggling are explicitly documented as limitations rather than missing coverage.

    Maintenance

    ActivityStale
    ResponsivenessSlow

    Resources