Skip to main content
Glama
arco-greendigit

coda-mcp-readonly

by arco-greendigit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to coda-mcp-readonly

No user-submitted related servers found.

    Related Servers

    • Coda MCP Server

      orellazri
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Coda documents, allowing operations like listing, creating, reading, updating, and duplicating pages.
      19
      5,790 npm
      63
      MIT

    • readonly-mcp-server

      Varun4b1
      F
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server with configurable transport (stdio or HTTP+SSE), API key authentication, and scope-based authorization for read and search operations on documents.
      -

    • gdoc-comments

      gxozer
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for reading/editing Google Docs content and managing comments, including listing, creating, replying, resolving, and reopening comments via the Docs API and Drive API.
      GPL 3.0

    • 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

    • mdgen-mcp

      Shien-Inc
      A
      license
      A
      quality
      C
      maintenance
      MCP server for mdgen that enables reading, writing, and managing mdgen documents from MCP clients like Claude Desktop and Codex CLI using your own mdgen account.
      5
      7 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.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    The tools are mostly distinct, but coda_get_page_content and coda_peek_page serve similar purposes—both retrieve page content with slight differences in format and length. This overlap could cause confusion, but all other tools clearly target different resources or actions.

    Naming Consistency5/5

    All tool names follow a consistent coda_ prefix followed by a verb_noun pattern (e.g., list_documents, get_page_content, resolve_link). The naming is uniform, using snake_case throughout, making it easy to predict tool functions.

    Tool Count5/5

    With 9 tools, the server is well-scoped for a read-only Coda API. Each tool serves a clear purpose in reading documents, pages, tables, and rows, without unnecessary bloat or missing essential operations.

    Completeness4/5

    For a read-only server, the tool surface covers the core lifecycle of reading Coda objects: documents, pages, tables, columns, and rows. Minor gaps exist, such as no separate tool to fetch a single column or table metadata, but these can be worked around with existing list endpoints.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources