Skip to main content
Glama
kimata1007

notion-ops-mcp

by kimata1007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to notion-ops-mcp

No user-submitted related servers found.

    Related Servers

    • notion-mcp-hono

      ldamoredev
      F
      license
      Not graded
      quality
      B
      maintenance
      Remote 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.
      -

    • NotionMCP Server

      tleeds1
      F
      license
      Not graded
      quality
      D
      maintenance
      A Python server that integrates MCP with Notion to automate documentation workflows and manage Notion pages via LLMs, supporting operations like creating, updating, and searching Notion content.
      1
      -

    • mcp-notion

      ftaricano
      A
      license
      B
      quality
      D
      maintenance
      MCP server for common Notion page workflows: search pages, inspect content, create structured pages, append rich blocks, and start documents from reusable templates.
      10
      MIT

    • notion-private-api-mcp

      kirvigen
      A
      license
      A
      quality
      C
      maintenance
      Unofficial Notion MCP server built on Notion's private API (token_v2 cookie). Gives LLM agents full read/write access to the entire workspace — no integration token and no per-page sharing.
      11
      9 npm
      4
      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 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one reads/fetches documents, the other creates or updates them. There is no overlap or ambiguity in their intended use.

    Naming Consistency5/5

    Both tool names follow the exact same pattern: a 'notion_' prefix, a verb ('read' or 'publish'), and an object ('document'). The naming is perfectly consistent and predictable.

    Tool Count3/5

    With only two tools, the server feels thin for the 'notion-ops' scope. However, each tool is broad and capable (bulk reads, conflict-safe writes), so it is borderline rather than severely underdeveloped.

    Completeness4/5

    The read and publish tools together cover searching/resolving, reading, creating, and updating documents, which covers most core workflows. The main gap is the lack of an explicit delete operation, but this is a minor omission given the server's apparent focus on content operations.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources