Grist MCP Server
Related Servers
Alternatives to Grist MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables 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.62 npm-
- AlicenseAqualityCmaintenanceMCP server that allows interaction with PocketBase databases, enabling record operations (fetch, list, create, update), file management, and schema migrations through natural language.2210 npm39MIT
- FlicenseNot gradedqualityCmaintenanceMCP server enabling natural-language querying of SQLite databases via schema discovery, GraphRAG retrieval, and safely guarded read-only SQL execution.-
- FlicenseNot gradedqualityDmaintenanceMCP server that provides SQLite database operations. Allows AI assistants to query, modify and manage SQLite databases through the Model Context Protocol.-
- AlicenseBqualityDmaintenanceAn MCP server that enables LLMs to interact with Moxie CRM. Provides comprehensive tools for managing clients, contacts, projects, invoices, time tracking, and more.304 npm2MIT
- AlicenseNot gradedqualityDmaintenanceThis MCP server enables AI assistants to interact with a SQLite database through a spreadsheet-like interface, supporting operations such as querying, editing, importing Excel/CSV, and managing table structures via natural language.1ISC
TDQS
Scored across 54 tools
Most tools are distinct, but there is notable overlap between add_grist_records and add_grist_records_safe, and between filter_sql_query and execute_sql_query. Also, list_columns and get_table_schema both expose column structure, which could cause misselection.
The naming is mostly verb_noun (list_*, create_*, modify_*, delete_*), but there are inconsistencies: add_grist_records vs create_table/create_document, and filter_sql_query/execute_sql_query don't follow the verb_noun pattern. The 'grist' infix in some record tools is inconsistent with the rest.
54 tools is excessive for a single MCP server. While Grist is a complex platform, the tool surface could be consolidated (e.g., merging schema tools, reducing redundant record add variants) to reduce cognitive load.
The server covers the full hierarchy (organizations, workspaces, documents, tables, columns, records) with CRUD operations, plus access management, attachments, webhooks, schema tools, and exports. Minor gaps exist (e.g., no direct table data import/export beyond CSV/SQLite/Excel, no webhook queue inspection), but the core domain is well covered.