Grist MCP Server
Related Servers
Alternatives to Grist MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseAqualityCmaintenanceMCP server that allows interaction with PocketBase databases, enabling record operations (fetch, list, create, update), file management, and schema migrations through natural language.2243MIT
- FlicenseNot gradedqualityDmaintenanceMCP server enabling natural-language querying of SQLite databases via schema discovery, GraphRAG retrieval, and safely guarded read-only SQL execution.-

stoolap-mcpofficial
AlicenseNot gradedqualityBmaintenanceOfficial 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 npm1Apache 2.0- FlicenseNot gradedqualityDmaintenanceMCP server that provides SQLite database operations. Allows AI assistants to query, modify and manage SQLite databases through the Model Context Protocol.-
- AlicenseBqualityCmaintenanceAn MCP server that enables LLMs to interact with Moxie CRM. Provides comprehensive tools for managing clients, contacts, projects, invoices, time tracking, and more.309 npm3MIT
TDQS
Scored across 54 tools
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).
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.
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.
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.