Grist Automation

What This Skill Does

This skill automates Grist operations using the Composio Grist toolkit via Rube MCP. It allows users to programmatically interact with Grist spreadsheets and data. This is useful for data analysts and developers.

When to Use

Automate data entry into Grist. Generate reports from Grist data. Trigger actions based on Grist data changes. Manage Grist user permissions. Sync Grist data with other systems.

Key Features

Uses Rube MCP for tool discovery and execution. Requires an active Grist connection. Provides a structured workflow pattern. Emphasizes schema compliance for arguments. Offers tool discovery via RUBE_SEARCH_TOOLS.

Manual Installation

Grist Automation via Rube MCP

Automate Grist operations through Composio's Grist toolkit via Rube MCP. Toolkit docs: composio.dev/toolkits/grist

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Grist connection via RUBE_MANAGE_CONNECTIONS with toolkit grist Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit grist If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Grist operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

queries: [{use_case: "your specific Grist task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["grist"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {}

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Powered by Composio