Tabulic

Workspaces and agents

Accounts, workspaces, handles, agents and connections.

Account

You sign in to Tabulic with one email address. Your account holds your plan, the workspaces you own and your agents. It lives outside every workspace, so a downloaded workspace carries nothing about your account except the names of the agents in its history.

Workspace

A workspace is one self-contained body of data: its tables, rows, change history, apps and the settings for each agent and app in it. Each workspace is stored as a single file.

Every workspace has a handle: a short name, unique across Tabulic, that is part of its address and never changes.

https://app.tabulic.com/w/<handle>                 the workspace's screens
https://app.tabulic.com/w/<handle>/apps/<name>     an app's page
https://app.tabulic.com/w/<handle>/v1/             the App API

The display name can repeat and can be changed. The owner creates workspaces on their account page, or an agent does with create_workspace if the owner allowed it.

Owner

The owner is the single person a workspace belongs to, and the only one who can approve or roll back changes, or change what agents and apps may do. The owner’s own writes never wait for approval.

Agent

An agent is a named identity under which an AI tool acts, such as “Claude” or “Claude Code”. You name it when you connect the tool.

  • It belongs to your account. One connection reaches every workspace you let it.
  • In each workspace it has its own scope and approval rules.
  • It keeps its name and history across reconnections. Reconnect and choose the existing agent to carry on as it.

Connect two tools under two names (“Claude”, “ChatGPT”) to tell their changes apart and give them different access.

Connection

A connection is one authorization through which a host acts as an agent, or a browser or script acts as an app. Tabulic runs its own OAuth sign-in, so connecting never involves copying a key into a chat. An agent or app can have several connections over time; disconnecting one revokes it at once and leaves the history alone.

The connector

All AI tools use one MCP connector address:

https://mcp.tabulic.com

It speaks MCP over Streamable HTTP with OAuth. The server tells every agent, in its instructions:

Tabulic stores tables for the person you work for, in workspaces: call list_workspaces first, and name the workspace (its handle) in every other tool. Every change you make is recorded and can be reviewed and rolled back by them. Some writes wait for their approval: when a write comes back with status “pending”, tell the person and do not retry it. To build an app on a workspace’s tables, call app_guide first.

See the MCP tools reference.

On this page