Skip to main content
Glama
Grist MCP Server
by nic01asFr

Related Servers

Alternatives to Grist MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables reading and writing to Grist documents via natural language through MCP tools, allowing users to manage data, schemas, documents, and more using AI assistants like Perplexity.
      -
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that allows interaction with PocketBase databases, enabling record operations (fetch, list, create, update), file management, and schema migrations through natural language.
      22
      43
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server enabling natural-language querying of SQLite databases via schema discovery, GraphRAG retrieval, and safely guarded read-only SQL execution.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Official MCP server for Stoolap, an embedded SQL database written in Rust. Lets assistants run SQL queries and transactions, inspect and change schemas, and do vector search over a local file or in-memory database, with a read-only mode.
      9 npm
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides SQLite database operations. Allows AI assistants to query, modify and manage SQLite databases through the Model Context Protocol.
      -

    TDQS

    C2.8/5.0

    Scored across 54 tools

    Disambiguation4/5

    Most tools target a distinct resource+action (create_workspace, list_documents, delete_column), so an agent can usually select correctly. A few pairs overlap: add_grist_records vs add_grist_records_safe do the same operation with different validation, and filter_sql_query vs execute_sql_query both run SQL (though descriptions distinguish simple vs complex cases).

    Naming Consistency4/5

    The dominant pattern is consistent French verb_noun (create_/list_/describe_/modify_/delete_ + resource). Minor deviations exist: get_table_schema uses 'get' where others use 'describe', the 'grist' qualifier appears only on add/update/delete records, and downloads use verb_noun_noun (download_document_sqlite). These are readable and don't break predictability.

    Tool Count2/5

    54 tools is very heavy for agent navigation, well past the 25+ 'too many' threshold. The breadth mirrors Grist's real API (orgs, workspaces, docs, tables, columns, records, access, downloads, attachments, webhooks, schemas), so few tools are truly redundant, but the surface is unwieldy and would benefit from consolidation.

    Completeness4/5

    Coverage is broad and near-complete CRUD across the hierarchy plus specialized areas (schema validation/creation, references, attachments, webhooks, access, exports). Minor gaps exist, e.g. no create_organization and no single-record get (only list_records), but these are edge operations an agent can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data