How to integrate Grist MCP with Codex

Framework Integration Gradient
Grist Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Grist MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Grist MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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 & Triggers

Tools
Add RecordsTool to add records to a specified table in a Grist document.
Create DocumentTool to create a document in a workspace.
Create SCIM UserTool to create a new SCIM user.
Create TableTool to create tables in a document.
Create Document WebhookTool to create a new webhook for a specified document.
Delete AttachmentTool to delete a specified attachment from a Grist document.
Delete ColumnTool to delete a column from a Grist document table.
Delete Grist Table RecordsTool to delete records from a specified Grist table.
Delete SCIM UserTool to delete a specified user via SCIM.
Delete WebhookTool to delete a webhook from a Grist document.
Download All Attachments ArchiveTool to download all attachments from a Grist document as a .
Download AttachmentTool to download the binary data of an attachment.
Download Grist Attachment ContentTool to download the raw bytes of an attachment.
Fetch Column MetadataTool to fetch metadata for a specific column in a Grist document table.
Fetch Document MetadataTool to fetch metadata for a specified Grist document.
Fetch Table MetadataTool to retrieve metadata for a specified table in a Grist document.
Get Org AccessTool to fetch org access details.
Get UsersTool to retrieve a list of users via SCIM v2.
List AttachmentsTool to list all attachments in a Grist document.
List ColumnsTool to list all columns in a specified Grist table.
List OrganizationsTool to list all organizations accessible to the authenticated user.
List RecordsTool to retrieve records from a specified table within a Grist document.
List TablesTool to list all tables within a specified document.
List WebhooksTool to list webhooks configured for a document.
List WorkspacesTool to list all workspaces and documents accessible to the authenticated user on the current site.
Run SQL QueryTool to execute a read-only SQL SELECT query on a Grist document.
Update Column MetadataTool to update metadata for one or more columns in a Grist document table.
Update Document MetadataTool to update metadata for a specified Grist document.
Update RecordsTool to update records in a specified table within a document.
Update Table MetadataTool to update metadata for a specified table.
Update WebhookTool to update an existing webhook for a specified document.
Upload AttachmentTool to upload one or more attachments to a Grist document.

Conclusion

You've successfully integrated Grist with Codex using Composio's Rube MCP server. Now you can interact with Grist directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Grist operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Grist operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Grist MCP Agent with another framework

FAQ

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 Codex?

Yes, you can. Codex 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.