Get started

Grist for AI agents

Grist is a relational spreadsheet that combines spreadsheet flexibility with database structure, used to build lightweight custom apps on top of data. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect GristSee the 30 actions ↓
ProductivityAPI keyMCP + RESTgetgrist.com
AUDIT LOG · GRISTPOLICY: acme-support
09:41:07 · claude · u_8f2read
grist.list_tables
List Tables✓ allowed · 212ms
09:41:08 · claude · u_8f2read
grist.get_users
Get Users✓ allowed · 164ms
09:41:09 · claude · u_8f2write
grist.create_table
Create Table✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
grist.delete_column
Delete Column✕ blocked · policy: deny
EVERY GRIST CALL, ON THE RECORD
01 · USE CASES

What agents do in Grist.

01

Read records from a table

List records in a Grist table to answer a question about current inventory or project status.

02

Add a new record

Add a new row to a table with details submitted through a request or form.

03

Delete records with confirmation

Delete a batch of table records only after a document owner confirms the cleanup.

02 · ACTIONS

30 Grist actions, graded by risk.

Every Grist action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

12

Look things up. Allowed by default.

  • grist.get_users
    Get Users
  • grist.list_tables
    List Tables
  • grist.list_columns
    List Columns
  • grist.list_records
    List Records
  • grist.list_webhooks
    List Webhooks
  • grist.get_org_access
    Get Org Access
  • grist.list_workspaces
    List Workspaces
  • grist.list_attachments
    List Attachments
  • grist.list_organizations
    List Organizations
  • grist.download_attachment
    Download Attachment
  • grist.fetch_table_metadata
    Fetch Table Metadata
  • grist.fetch_document_metadata
    Fetch Document Metadata

write

12

Create and change things. Allow, or ask the user first.

  • grist.add_records
    Add Records
  • grist.create_table
    Create Table
  • grist.create_webhook
    Create Document Webhook
  • grist.update_records
    Update Records
  • grist.update_webhook
    Update Webhook
  • grist.create_document
    Create Document
  • grist.create_scim_user
    Create SCIM User
  • grist.update_table_metadata
    Update Table Metadata
  • grist.update_column_metadata
    Update Column Metadata
  • grist.update_document_metadata
    Update Document Metadata
  • grist.run_sql_query
    Run SQL Query
  • grist.upload_attachment
    Upload Attachment

destructive

6

Delete, cancel or archive. Ask first, or deny outright.

  • grist.delete_column
    Delete Column
  • grist.delete_records
    Delete Grist Table Records
  • grist.delete_webhook
    Delete Webhook
  • grist.delete_scim_user
    Delete SCIM User
  • grist.delete_attachment
    Remove Unused Attachments
  • grist.download_all_attachments_archive
    Download All Attachments Archive
03 · HOW IT WORKS

Grist in three steps.

  1. 01Your users connect GristThey add their Grist api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Table” can wait for the user, and “delete Column” can be denied outright.
  3. 03Any agent can actYour agent calls Grist through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('grist', {
  read: 'allow',
  write: 'ask',        // create_table
  destructive: 'deny',  // delete_column
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Grist connects.

Users add their Grist api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Grist connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Grist from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More productivity apps.

Notion57 actionsAirtable27 actionsConfluence70 actionsClickUp164 actionsAmazing Marvin10 actionsRentman130 actionsHub Planner122 actionsCoda110 actions
ALL PRODUCTIVITY APPS →
07 · FAQ

Grist and Arc0, answered.

Q01

Can I use Grist with Claude, ChatGPT or Cursor?

Yes. Connect Grist to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Grist actions you allow.

Q02

How do users connect Grist?

Users add their Grist api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Grist actions can my agent take?

30 in total: 12 read, 12 write and 6 destructive, such as “create Table”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Grist?

Yes. Actions like “delete Column” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Grist too?

Yes. The same Grist connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Grist into your agent.

Your users connect Grist once, under your brand. Your agent gets 30 actions behind your policies, with every call on the record.

Connect GristBrowse all apps →

Free to build · MCP + REST · Audit log on every plan