Skip to main content
Glama
Taewoong1378

Notion ReadOnly MCP Server

by Taewoong1378
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Notion ReadOnly MCP Server

No user-submitted related servers found.

    Related Servers

    • nooon

      corrupt952
      A
      license
      Not graded
      quality
      A
      maintenance
      A lightweight, read-only MCP server for Notion that enables searching, reading pages, and querying databases with token-efficient output and smart caching.
      18 npm
      5
      MIT

    • AI OS MCP Server

      cockimitu-ops
      F
      license
      A
      quality
      C
      maintenance
      Exposes a Notion-synced AI OS as read-only MCP tools, enabling MCP-compatible AI clients to search the vault, fetch page contents, list projects, and check project statuses without scraping public links.
      4
      -

    • notion-mcp-fast

      lucid-jin
      A
      license
      Not graded
      quality
      D
      maintenance
      Fast, read-only MCP server for Notion that reads directly from local SQLite cache, enabling instant access to Notion pages, databases, and users without API calls or rate limits.
      1
      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.
      3 npm
      1
      MIT

    • Restora

      tahabakri
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that exposes your local Notion backups to AI agents — query databases, read pages, search a backed-up workspace. Offline by default: no LLM calls, no telemetry, no cloud.
      6
      1
      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

    C2.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific Notion resources (blocks, pages, databases, comments, properties), but 'API-retrieve-a-block' and 'API-get-block-children' could cause confusion as both relate to blocks with overlapping retrieval functions. The descriptions help clarify, but the boundary isn't perfectly clear.

    Naming Consistency3/5

    The naming follows a mostly consistent 'API-[verb]-a-[noun]' pattern for seven tools, but 'API-get-background-result' and 'API-get-one-pager' deviate with different verb structures ('get' vs 'retrieve') and compound nouns. This mixed convention reduces predictability, though the names remain readable.

    Tool Count5/5

    With 8 tools, the count is well-scoped for a read-only Notion server, covering key retrieval operations without bloat. Each tool serves a clear purpose, making the set manageable and focused on the server's stated functionality.

    Completeness4/5

    For a read-only server, the tool set provides comprehensive coverage of Notion's core resources (pages, blocks, databases, comments, properties) and includes useful utilities like background result retrieval. A minor gap exists in lacking a tool for listing/searching across multiple resources, but agents can work around this with the available retrieval tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources