MCP tools
Every tool Tabulic gives a connected agent, with its inputs and behavior.
Connect to https://mcp.tabulic.com (MCP over Streamable HTTP, OAuth). Every tool except list_workspaces and create_workspace takes a workspace argument: the workspace’s handle.
Tables and columns are named by name. Write tools answer with a result like:
{ "status": "applied", "changeset": 42, "rows_affected": 3 }or, when the agent’s approval rules hold it back:
{ "status": "pending", "changeset": 43, "rows_affected": 25, "waits_for": "bulk-update", "message": "…" }"status": "pending": tell the person, and don’t retry. Check later with changeset_status.Workspaces
| Tool | Inputs | Does |
|---|---|---|
list_workspaces | none | The workspaces you can reach: handle, name, and what you may do in each. Call this first. |
create_workspace | handle, name | Creates a workspace, if the person allowed it. You get full access. handle: 3–30 lowercase letters, digits and single hyphens, unique, permanent. |
Reading
| Tool | Inputs | Does |
|---|---|---|
describe_schema | workspace | The tables you can read and their columns, which you may write, whether you may change the schema, and your approval rules. |
query | workspace, table, filter?, sort?, limit? | Rows from one table. sort: [{"column", "desc"?}]. limit: default 100, at most 1000. Says how many inserted rows are still pending. |
sql_query | workspace, sql | One read-only SELECT (or WITH … SELECT) over your tables by name, with _row_id for each row’s ID. At most 1000 rows (truncated: true if more matched). Runs on a private copy, limited to your scope. Prefer query for simple reads. |
Writing rows
| Tool | Inputs | Default |
|---|---|---|
insert_rows | workspace, table, rows (each maps column names to values) | applies |
update_rows | workspace, table, filter, values | applies up to 10 rows, waits above |
delete_rows | workspace, table, filter | waits |
write_batch | workspace, label, writes | one changeset, all or nothing (below) |
filter is required for updates and deletes; {} selects every row. See Data types and filters.
write_batch
Up to 100 writes, each one of:
{ "insert": "Orders", "rows": [{ "Item": "Desk", "Qty": 2 }] }
{ "update": "Holdings", "filter": {}, "values": { "Qty": 0 } }
{ "delete": "Orders", "filter": { "column": "Status", "op": "=", "value": "void" } }Every write applies, or if any would wait, the whole batch waits. One invalid write refuses the batch. Every write picks its rows as the batch arrives, so it doesn’t see the batch’s earlier writes.
Grouping and pending changes
| Tool | Inputs | Does |
|---|---|---|
begin_changeset | workspace, label | Starts a new, named group, so the person reviews and rolls it back as one, e.g. “Import clients”. |
changeset_status | workspace, changeset | Whether one of your changesets is pending, applied, rejected, withdrawn or expired. |
withdraw_pending | workspace, changeset | Takes back one of your pending changesets. Nothing in it is applied. |
There is no tool to approve, reject or roll back. Those are the owner’s, on Tabulic’s screens.
Schema
Needs the change the schema permission in your scope, except on tables you created.
| Tool | Inputs | Default |
|---|---|---|
create_table | workspace, table, columns: [{name, type}] | applies; you get read and write on it |
add_column | workspace, table, column: {name, type} | applies |
rename_table | workspace, table, to | applies; nothing that refers to it breaks |
rename_column | workspace, table, column, to | applies |
change_column_type | workspace, table, column, type | waits. Reports which values convert; values that can’t become empty, with the originals kept |
drop_column | workspace, table, column | waits; data kept so it can be restored |
drop_table | workspace, table | waits; data kept so it can be restored |
Column types: text, number, boolean, date, datetime.
Apps
| Tool | Inputs | Does |
|---|---|---|
app_guide | workspace | How to build an app on these tables: the API address, the tabulic.js script tag, the tabulic.css stylesheet, tables’ stable IDs, an example page, the rules, and the pages already published. Creates nothing. Call this before building an app. |
publish_page | workspace, name, title, html | Publishes an app’s page, one self-contained HTML file (at most 1 MB), and returns its url and version. Same name updates it. Needs the publish app pages permission. |
read_page | workspace, page (name or link) | The current HTML of a published page, to edit and publish again. Read it right before editing. |
Inline review
Write tools that can wait carry an MCP App resource (ui://tabulic/changeset). In hosts that show MCP Apps (Claude, ChatGPT, VS Code, Cursor), a pending write shows its diff in the conversation, with a Review and approve button that opens it on Tabulic’s screens. Other hosts show the same as text.
Recommended agent workflow
list_workspaces, thendescribe_schemaon the one you need.- Read with
query; usesql_queryfor joins and aggregates. - For a multi-step task,
begin_changesetwith a clear label, or send related writes as onewrite_batch. - If a write is pending, tell the person and stop retrying it.
- To build a UI,
app_guide→ write the page →publish_page→ send the person the link.