# How to integrate Grist MCP with Claude Code ```json { "title": "How to integrate Grist MCP with Claude Code", "toolkit": "Grist", "toolkit_slug": "grist", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/grist/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/grist/framework/claude-code.md", "updated_at": "2026-05-12T10:14:24.273Z" } ``` ## Introduction Manage your Grist directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## Also integrate Grist with - [OpenAI Agents SDK](https://composio.dev/toolkits/grist/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/grist/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/grist/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/grist/framework/codex) - [OpenClaw](https://composio.dev/toolkits/grist/framework/openclaw) - [Hermes](https://composio.dev/toolkits/grist/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/grist/framework/cli) - [Google ADK](https://composio.dev/toolkits/grist/framework/google-adk) - [LangChain](https://composio.dev/toolkits/grist/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/grist/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/grist/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/grist/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/grist/framework/crew-ai) ## TL;DR - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Grist to Claude Code ### Connecting Grist to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## What is the Grist MCP server, and what's possible with it? The Grist MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Grist account. It provides structured and secure access to your spreadsheets and documents, so your agent can perform actions like adding records, creating tables, managing documents, and handling attachments on your behalf. - Automated data entry and record management: Instruct your agent to add, update, or delete records in specific Grist tables, streamlining your workflows and reducing manual input. - Table and document creation: Let your agent create new tables or entire documents in your workspaces, helping you quickly set up and expand your data structures as your needs grow. - Attachment and file management: Ask your agent to remove unwanted attachments from Grist documents, keeping your files organized and storage efficient. - Custom webhook integration: Have your agent register or delete webhooks for documents, enabling real-time notifications and integrations with other tools or services you rely on. - User and access provisioning via SCIM: Direct your agent to create or delete SCIM users as needed, making it easy to manage who has access to your Grist environment. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `GRIST_ADD_RECORDS` | Add Records | Add one or more records to a Grist table. First use GRIST_LIST_WORKSPACES to get docId, GRIST_LIST_TABLES to get tableId, and GRIST_LIST_COLUMNS to get column IDs for the fields mapping. | | `GRIST_CREATE_DOCUMENT` | Create Document | Creates a new Grist document in a specified workspace. Use this tool when you need to add a new spreadsheet document to a workspace. Requires a valid workspace ID (obtainable via GRIST_LIST_WORKSPACES) and a document name. | | `GRIST_CREATE_SCIM_USER` | Create SCIM User | Tool to create a new SCIM user. Use when provisioning new user accounts via SCIM. Run after gathering all required user details. | | `GRIST_CREATE_TABLE` | Create Table | Tool to create tables in a document. Use after confirming the document ID. Creates one or more tables with specified columns in the given document. | | `GRIST_CREATE_WEBHOOK` | Create Document Webhook | Tool to create a new webhook for a specified document. Use when you need to register webhook endpoints for document events in Grist. Run after confirming document ID. | | `GRIST_DELETE_ATTACHMENT` | Remove Unused Attachments | Remove unused attachments from a Grist document to free up storage space. IMPORTANT: This action removes ALL attachments that are not currently referenced by any cell in the document. It does NOT delete a specific attachment by ID. To remove a specific attachment: 1. First remove its reference from the Attachments column cell that contains it 2. Then call this action to clean up the now-unreferenced file Attachments become "unused" when they are no longer referenced by any Attachments-type cell. Grist normally retains unreferenced attachments for a period to allow undo operations. This action removes them immediately (or only expired ones if expired_only=true). | | `GRIST_DELETE_COLUMN` | Delete Column | Tool to delete a column from a Grist document table. Use after confirming document, table, and column IDs. | | `GRIST_DELETE_RECORDS` | Delete Grist Table Records | Tool to delete records from a specified Grist table. Use when you need to remove specific rows by their IDs. Use after confirming the row IDs exist. | | `GRIST_DELETE_SCIM_USER` | Delete SCIM User | Delete a user from the Grist organization by their numeric user ID. Use GRIST_GET_USERS first to find the user's ID. Falls back to org access API if SCIM is not enabled. Note: Cannot delete your own account. | | `GRIST_DELETE_WEBHOOK` | Delete Webhook | Permanently removes a webhook from a Grist document. Use this tool when you need to stop receiving notifications for document changes. First use GRIST_LIST_WEBHOOKS to find the webhook_id you want to delete. This action is destructive and cannot be undone. | | `GRIST_DOWNLOAD_ALL_ATTACHMENTS_ARCHIVE` | Download All Attachments Archive | Download all attachments from a Grist document as a single archive file (.zip or .tar). Use this to bulk-download attachments. Ensure the document has attachments before calling (check with GRIST_LIST_ATTACHMENTS). Returns an empty archive if no attachments exist. | | `GRIST_DOWNLOAD_ATTACHMENT` | Download Attachment | Download a file attachment from a Grist document. Returns the file content as a downloadable file. Use GRIST_LIST_ATTACHMENTS first to get valid attachment IDs. | | `GRIST_FETCH_DOCUMENT_METADATA` | Fetch Document Metadata | Tool to fetch metadata for a specified Grist document. Use after obtaining the document ID. | | `GRIST_FETCH_TABLE_METADATA` | Fetch Table Metadata | Tool to retrieve metadata for a specified table in a Grist document. Use when you need to inspect table schema details before data operations. | | `GRIST_GET_ORG_ACCESS` | Get Org Access | Retrieves the list of users who have access to a Grist organization along with their access roles (owners, editors, viewers). Use this to find user IDs, emails, or check access permissions within an organization. Useful for user management tasks. | | `GRIST_GET_USERS` | Get Users | Tool to retrieve a list of users via SCIM v2. Use when you need to page through and filter enterprise users in Grist. | | `GRIST_LIST_ATTACHMENTS` | List Attachments | Tool to list all attachments in a Grist document. Use after confirming the document ID to retrieve attachment metadata. | | `GRIST_LIST_COLUMNS` | List Columns | Tool to list all columns in a specified Grist table. Use after selecting the document and table to inspect column metadata. | | `GRIST_LIST_ORGANIZATIONS` | List Organizations | Tool to list all organizations accessible to the authenticated user. Use when you need to select a Grist organization for subsequent operations. | | `GRIST_LIST_RECORDS` | List Records | Tool to retrieve records from a specified table within a Grist document. Use when you need to fetch rows by applying optional filters, sorting, limits, or hidden columns. Example: list records where pet is 'cat' sorted by '-age'. | | `GRIST_LIST_TABLES` | List Tables | Tool to list all tables within a specified document. Use after obtaining the document ID to retrieve its tables. | | `GRIST_LIST_WEBHOOKS` | List Webhooks | List all webhooks configured for a Grist document. Returns webhook configuration details (URL, event types, table binding) and delivery status information. Use this to inspect, audit, or manage webhooks for a document. Requires a valid document ID obtained from GRIST_LIST_WORKSPACES or GRIST_CREATE_DOCUMENT. | | `GRIST_LIST_WORKSPACES` | List Workspaces | Tool to list all workspaces and documents accessible to the authenticated user on the current site. Use when you need to select a workspace or document for subsequent operations. | | `GRIST_RUN_SQL_QUERY` | Run SQL Query | Tool to execute a read-only SQL SELECT query on a Grist document. Use after confirming the document ID and preparing a valid SQL SELECT statement. | | `GRIST_UPDATE_COLUMN_METADATA` | Update Column Metadata | Updates metadata (label, type, description, formula, etc.) for one or more columns in a Grist table. Use List Columns first to get valid column IDs. Warning: changing 'label' may rename the column ID unless 'untieColIdFromLabel' is set to true. | | `GRIST_UPDATE_DOCUMENT_METADATA` | Update Document Metadata | Tool to update metadata for a specified Grist document. Use when you need to rename or pin/unpin a document after obtaining its ID. | | `GRIST_UPDATE_RECORDS` | Update Records | Update existing records in a Grist table by their row IDs. Use this tool to modify field values for one or more records in a specified document and table. First use GRIST_LIST_RECORDS to obtain the record IDs you want to update. Supports batch updates - you can update multiple records in a single call. The API uses PATCH semantics, meaning only specified fields are updated; unspecified fields remain unchanged. IMPORTANT: When updating multiple records in a batch, all records must specify the exact same set of field names (e.g., if updating Name and Age for record 1, you must also update Name and Age for record 2). | | `GRIST_UPDATE_TABLE_METADATA` | Update Table Metadata | Update metadata properties for a table in a Grist document. Currently the main updatable property is 'onDemand' which controls lazy loading of table data. Use List Tables to find valid table IDs first. | | `GRIST_UPDATE_WEBHOOK` | Update Webhook | Update an existing webhook configuration for a Grist document. Use to modify webhook settings such as URL, event types, enabled status, or target table. Requires valid document ID (from GRIST_LIST_WORKSPACES) and webhook ID (from GRIST_LIST_WEBHOOKS). Only provided fields will be updated; omitted fields remain unchanged. | | `GRIST_UPLOAD_ATTACHMENT` | Upload Attachment | Upload one or more file attachments to a Grist document. Returns attachment IDs that can be used to link files to records in Attachments-type columns. First use GRIST_LIST_WORKSPACES to get a valid document ID. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Grist MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Grist account. It provides structured and secure access so Claude can perform Grist operations on your behalf. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Claude Pro, Max, or API billing enabled Anthropic account - Composio API Key - A Grist account - Basic knowledge of Python or TypeScript ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```bash # macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash # Windows PowerShell irm https://claude.ai/install.ps1 | iex # Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd ``` ### 2. Set up Claude Code Open a terminal, go to your project folder, and start Claude Code: - Claude Code will open in your terminal - Follow the prompts to sign in with your Anthropic account - Complete the authentication flow - Once authenticated, you can start using Claude Code ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["grist"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http grist-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['grist'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http grist-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Grist MCP to Claude Code In your terminal, add the MCP server using the command from the previous step. The command format is: - claude mcp add registers a new MCP server with Claude Code - --transport http specifies that this is an HTTP-based MCP server - The server name (grist-composio) is how you'll reference it - The URL points to your Composio Tool Router session - --headers includes your Composio API key for authentication After running the command, close the current Claude Code session and start a new one for the changes to take effect. ```bash claude mcp add --transport http grist-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY" # Then restart Claude Code exit claude ``` ### 8. Verify the installation Check that your Grist MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your grist-composio entry in the list - This confirms that Claude Code can now access Grist tools If everything is wired up, you should see your grist-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Grist The first time you try to use Grist tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Grist - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Grist authorization flow - Return to the terminal and start using Grist through Claude Code Once authenticated, you can ask Claude Code to perform Grist operations in natural language. For example: - "Add new sales data to Q2 table" - "Create a document for project planning" - "Delete outdated rows from inventory sheet" ## Complete Code ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["grist"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http grist-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['grist'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http grist-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Grist with Claude Code using Composio's MCP server. Now you can interact with Grist directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Grist operations - Secure authentication through Composio's managed MCP - Tool Router for dynamic tool discovery and execution Next steps: - Try asking Claude Code to perform various Grist operations - Add more toolkits to your Tool Router session for multi-app workflows - Integrate this setup into your development workflow for increased productivity You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities. ## How to build Grist MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/grist/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/grist/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/grist/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/grist/framework/codex) - [OpenClaw](https://composio.dev/toolkits/grist/framework/openclaw) - [Hermes](https://composio.dev/toolkits/grist/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/grist/framework/cli) - [Google ADK](https://composio.dev/toolkits/grist/framework/google-adk) - [LangChain](https://composio.dev/toolkits/grist/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/grist/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/grist/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/grist/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/grist/framework/crew-ai) ## Related Toolkits - [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly. - [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place. - [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations. - [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals. - [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem. - [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity. - [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently. - [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place. - [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place. - [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place. - [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place. - [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives. - [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions. - [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date. - [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page. - [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes. - [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights. - [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Grist MCP? With a standalone Grist MCP server, the agents and LLMs can only access a fixed set of Grist tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Grist and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Claude Code? Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Grist tools. ### Can I manage the permissions and scopes for Grist while using Tool Router? Yes, absolutely. You can configure which Grist scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Grist data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)