Grist
Read, add, update, upsert and delete Grist records; run read-only SQL; manage tables and columns; browse orgs, workspaces and docs.
About
Grist ships in the w6w first-party pack. It declares 15 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.grist- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Spreadsheets · Databases · Productivity
Overview
Grist is a spreadsheet whose cells are backed by a real SQLite database, so it can be queried like one — and this app reads and writes Grist records, tables and columns, plus runs read-only SQL, over the Grist API, against both Grist’s hosted service and a self-hosted install.
It covers the full record lifecycle — list, add, update, upsert, delete — with exact-match filtering, schema actions to create tables and add columns, a CSV/TSV export, and a run-sql action for anything a simple filter can’t express, such as joins, aggregates or an ordering the records endpoint doesn’t support. Discovery actions for orgs, workspaces and docs resolve the ids the other actions need, since a document id has to come from somewhere before you can act on it.
Good for treating a Grist doc as a lightweight database behind a workflow — appending form submissions as rows, updating a record when an external event fires, running a report query on a schedule, or building a table and its columns as part of a setup step.
Build with Grist
Three routes to the same 15 actions. The Workflow tab is generated from Grist's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Add Columns
add-columns Add one or more columns to a table, including formula and reference columns.
Describe Document
describe-doc Fetch a document's metadata — name, your access level, and the workspace and org it belongs to. Reads no data.
Download Table as CSV/TSV
download-table Export one table as delimited text, exactly as Grist's own export produces it. Returns the file body as a string.
List Columns
list-columns List a table's columns with their IDs, labels, types and formulas — the vocabulary every other record call uses.
List Organizations
list-orgs List the team sites and personal areas this connection can reach. Takes no parameters.
List Records
list-records Fetch records from a table, optionally filtered by exact column values and sorted. Returns all matches unless `limit` is set.
List Tables
list-tables List a document's tables by their normalized IDs, optionally with every column's metadata inline.
List Workspaces and Documents
list-workspaces List an organization's workspaces with every document inside them — the way to discover document IDs.
Run SQL Query
run-sql Run a read-only SELECT against the document's SQLite database, with bound parameters. Use for joins, aggregates and paging.
Update Records
update-records Patch existing records by row ID. Only the columns you name are changed; send null to clear one.
Upsert Records
upsert-records Add or update records matched on column values rather than row ID. Creates when nothing matches.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Grist's real ids.
{
"manifestVersion": "2",
"name": "grist-example",
"steps": [
{
"id": "add-columns",
"uses": {
"app": "io.w6w.grist",
"action": "add-columns",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"docId": "<docId>",
"tableId": "<tableId>",
"columns": "<columns>"
}
}
]
}Here are some of the things you can do
-
Add Columns
performadd-columns -
Add Records
performadd-records -
Create Tables
performcreate-tables -
Describe Document
readdescribe-doc -
Download Table as CSV/TSV
readdownload-table
+10 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Grist, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Grist. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "add-records",
payload: {
docId: "<value>",
tableId: "<value>",
records: "<value>",
// noparse: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action add-records --payload '{"docId":"<value>","tableId":"<value>","records":"<value>"}'Give an AI agent Grist — without giving it Grist's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.grist#add-columns",
"input": {
"docId": "<docId>",
"tableId": "<tableId>",
"columns": "<columns>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Grist connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Grist's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Grist itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Grist declares its own checks, so its health is a property of the app rather than something the host guesses at.
Grist platform status
Grist server reachable
Unauthenticated `GET <site>/status?db=1` against this connection's Grist server — proves the host resolves, the app is serving, and its home database answers.