Connect TableThis to your AI client

1. The connector URL

Every client below takes the same URL, and no other setting:

You do not need an account before you start. The client sends you to TableThis to sign up or log in, and you land back in the client with the connection made. A new account gets a free Personal workspace, which the client can use immediately. If you are running TableThis on your own server, use that server's /mcp URL instead.

2. Connect a client

Claude Code

1. Run claude mcp add --transport http tablethis https://app.tablethis.ai/mcp in your terminal.
2. Open a session, run /mcp, and choose Authenticate.

Claude

1. Open Settings, then Connectors.
2. Choose Add custom connector and paste the URL above.
3. Choose Connect, then sign up or log in when TableThis asks.

This works in Claude on the web, in Claude Desktop, in Cowork, and on mobile. On Team and Enterprise plans, an owner adds the connector for the organization before members can use it.

ChatGPT

1. Open Settings, then Connectors, then Advanced settings.
2. Turn on Developer mode.
3. Choose Create, name it TableThis, and paste the URL above.
4. Set Authentication to OAuth, then connect.

ChatGPT registers itself with TableThis, so the approval screen labels it an unverified app. That label reflects how the app registered, not what it can do: you still choose the permissions it receives. On Business and Enterprise plans, an admin turns on Developer mode first.

Other MCP clients

Any client that supports remote MCP servers with OAuth 2.1 works the same way: point it at the URL above and complete the sign-in. Codex, Cursor, and Claude Code are all clients of this kind.

3. What an agent can do

An agent starts by listing the workspaces you belong to, and every other call names one of them. Beyond that, the tools fall into four groups.

Reading

List workspaces, tables, members, and documents. Describe a table's fields and types. Query records with filters, sorting, and paging. Read a document's Markdown, or search across documents and read the passages around a match. Poll a table for rows that changed since a cursor. Read audit history and pending changesets.

Editing one thing

Update one cell, one record, or one document in a single call. These are the tools an interactive artifact uses while you edit, and each one still creates an audited change with the same conflict checks as the reviewed workflow.

Larger changes

Create records, apply batches, and change tables, fields, or schema in one call. Move a table to another workspace, or archive and restore a workspace.

Proposing and reviewing

Propose a set of changes with an explanation and evidence, approve or reject them, apply the approved ones, and undo an audited change. This is the path to use when a person should see a change before it lands.

4. Permissions

The client asks for permissions when you connect, and you approve them on TableThis's own screen. These are the same descriptions that screen shows:

• app:write Edit your tables, fields, and records right away, and move tables to another workspace you can edit, and archive or restore workspaces you own
• changes:apply Apply approved changes
• changes:review Approve or reject suggested changes
• documents:read See your documents, folders, and passages
• documents:write Edit your documents right away
• records:write_proposals Suggest record changes for you to approve
• schema:write Suggest changes to tables and fields
• tables:read See your tables, records, history, and pending changes
• workspace:manage Add or remove workspace members, grant owner access, and enable or disable company-domain access, including joining existing and future verified accounts

Two things are worth knowing. An agent's access is never wider than your own: it sees a workspace because you are a member of it, and its role floors apply to every call. And a scheduled or always-on client cannot receive the immediate-write, review, or apply permissions at all — it can only suggest changes for a person to approve.

5. How writes work

A write carries the value it expects to replace. If someone else edited that cell first, the call comes back as a conflict with the current value instead of overwriting their work, and the agent retries against what is actually there. Two people editing the same table do not lose each other's changes.

Everything that changes is recorded. You can see who changed a cell, what it was before, and when, and undo it from the history view — and the same audit record exists whether a person or an agent made the change.

Content is only shared with the client you connected. TableThis does not train models on your workspace, and an agent reading a document receives the Markdown you wrote, not a rendered page. See the Privacy Policy for what is stored and for how long.

6. Troubleshooting

The client says the connection failed or was unauthorized

Access tokens expire. Remove the connector and add it again, then log in when TableThis asks — that issues a fresh token. If you changed or revoked the connection from the TableThis side, do the same.

A tool says a workspace was not found

That usually means the workspace is not one of yours, rather than that it does not exist. Ask the agent to list workspaces and use an id from that list.

A write reports a conflict

Someone changed the same cell or record first. The response carries the current value, and the agent should retry with that value as its starting point. Nothing was overwritten.

The client cannot see documents

Document permissions are separate from table permissions. A client connected without document access returns null for document operations and omits document history rather than failing, so grant the document permission and reconnect if the agent needs them.

A change is not visible yet

Search indexing lags a write by a few seconds. An empty search result immediately after a change is expected; wait a moment and search again.

7. Support

Email [email protected] for setup problems, connector bugs, or a question this page does not answer. Include the client you are using and what you asked it to do — that is usually enough to reproduce the problem.

TableThis is operated by Second Coffee, LLC. See the Terms of Service and Privacy Policy.