Skip to main content
Glama
Sign In
notion_personal_http

notion_personal_http

by Zach-zsc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to notion_personal_http

No user-submitted related servers found.

    Related Servers

    • 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,383 npm
      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,383 npm
      MIT

    • Notion MCP Server

      Matthias42778
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI agents and MCP-speaking clients such as Claude, Cursor, VS Code and ChatGPT to Notion using a single token, enabling them to create and edit pages, query databases, append blocks, apply templates, comment, and upload files in plain language. It runs headless for CI and background agents, keeps context usage low by loading only three tools, and supports batched mutations with idempotency and retries.
      4,383 npm
      MIT

    • Notion MCP Server

      rHill92561
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents headless, token-authenticated read/write access to a Notion workspace through MCP, using three context-efficient tools that cover 47 operations across pages, databases, blocks, templates, comments, users, and files. Supports creating and editing pages, querying and filtering databases, batch mutations with rollback and idempotency, markdown round-trips, and image/file uploads, runnable over stdio or HTTP in CI and self-hosted deployments.
      4,383 npm
      MIT

    • notion-mcp-server

      marcelobianchi696
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives MCP clients read/write access to Notion through a single token, letting AI agents search, create and edit pages, query databases, comment, and upload files in plain language. Works on every Notion plan and runs headless in CI, cron jobs, and self-hosted environments.
      4,383 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,383 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation3/5

    The tools overlap in that ask, submit, and reply all initiate some form of text task or message. While descriptions offer distinctions (ask waits, submit doesn't, reply is follow-up), the repeated boilerplate and the explicit recommendation to prefer submit+read over ask create uncertainty about when to use which. Boundaries are workable but not crystal clear.

    Naming Consistency5/5

    All tool names follow a consistent pattern: the prefix 'notion_personal_' followed by a single lowercase verb (ask, read, submit, reply). No mixing of conventions or camelCase. The pattern is predictable and readable.

    Tool Count5/5

    Four tools is well-scoped for a personal chat interface, covering initiation (submit/ask), reading (read), and follow-up (reply). No tool feels redundant or missing from a count perspective; each earns its place in the minimal lifecycle.

    Completeness4/5

    The set covers creating tasks, reading results, and replying in conversations. Minor gaps exist, such as listing existing threads or deleting/cancelling tasks, but these are either outside the core purpose or can be worked around via thread_id and read. Core workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources