Integration

AITable integration

AITable is a spreadsheet-database (the cloud edition of APITable). List, create, update and delete the records of a datasheet (up to 1000 read and 10 written per call), list and create or delete its fields, list its views, create datasheets, upload attachments, browse spaces and their folders and files, manage embed links (Pro plan or higher), run chat completions on an AITable AI agent (whitelisted accounts only), and, in enterprise-plan spaces and for their admins, manage space contacts: members, teams and roles. AITable reports some errors with HTTP 200 and success false in the answer (code 301 datasheet not found, 602 no permission): read success and code on every call. Sorting records by query and streaming chat are not exposed. Authentication is a personal API token from the AITable user settings, sent as a Bearer token.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in AITable.Built from the 31 AITable tools below, on the connection you add once.

What you can do with AITable

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Member, 4 operations

  • delete_memberDelete memberDELETEAgents: ask firstDeletes a member from a space's contacts.
  • get_memberGet memberGETAgents: ask firstReturns one member of a space (personal data): name, avatar, joined status, type (PrimaryAdmin, SubAdmin or Member), teams and roles, and with sensitiveData=true the email and phone number.
  • list_team_membersList team membersGETAgents: ask firstLists the members of a team, 1 to 1000 per page (default 100), personal data: name, avatar, status, type, teams and roles, and with sensitiveData=true email and phone number.
  • update_memberUpdate memberPUTAgents: ask firstChanges a member of a space: name, the teams it belongs to and its roles (unitIds). Returns the updated member.

Record, 4 operations

  • create_recordsCreate recordsPOSTAgents: ask firstCreates up to 10 records in a datasheet, with their field values keyed by field name (or id with fieldKey=id). Computed fields (formula, lookup, autonumber, created or modified time and by) cannot be written.
  • delete_recordsDelete recordsDELETEAgents: ask firstDeletes up to 10 records from a datasheet, given their ids: the rows and all their values are removed. data is true when they were deleted.
  • list_recordsList recordsGETAgents: ask firstLists the records of a datasheet, 1 to 1000 per page (default 100): all of them, those of a view, given ids, or those matching a formula. Each record has its id, timestamps and fields keyed by field name (or id with fieldKey=id).
  • update_recordsUpdate recordsPATCHAgents: ask firstUpdates up to 10 records of a datasheet: for each, only the fields sent change. Computed fields (formula, lookup, autonumber, created or modified time and by) cannot be written.

Role, 4 operations

  • create_roleCreate rolePOSTAgents: ask firstCreates a role in a space's contacts, with its name and order (from 2000 upward). Returns the new role.
  • delete_roleDelete roleDELETEAgents: ask firstDeletes a role from a space's contacts.
  • list_rolesList rolesGETAgents: ask firstLists the roles of a space, 1 to 1000 per page (default 100): unitId, name and order.
  • update_roleUpdate rolePUTAgents: ask firstChanges a role's name or order. Returns the updated role.

Embedlink, 3 operations

  • create_embed_linkCreate embed linkPOSTAgents: ask firstCreates an embed link (an iframe URL) for a datasheet, dashboard or form. Anyone with the link can view the data (readOnly by default); publicEdit or privateEdit allow editing. Same settings give the same link.
  • delete_embed_linkDelete embed linkDELETEAgents: ask firstDisables an embed link: its URL stops giving access.
  • list_embed_linksList embed linksGETAgents: ask firstLists the active embed links of a datasheet, dashboard or form: link id, URL and settings (deleted links are not returned). Each URL gives visitors access to the data.

Field, 3 operations

  • create_fieldCreate fieldPOSTAgents: ask firstAdds a field (column) to a datasheet, at most 200 per datasheet: its type, name and the attributes its type needs. Returns the new field's id and name.
  • delete_fieldDelete fieldDELETEAgents: ask firstDeletes a field (column) and its values from a datasheet.
  • list_fieldsList fieldsGETAgents: ask firstLists the fields (columns) of a datasheet, at most 200, in one answer: id, name, type, description, primary and editable flags and the type's attributes (options, precision, date format...). With viewId, in that view's order without hidden fields.

Node, 3 operations

  • get_nodeGet nodeGETAgents: ask firstReturns one file node: id, name, type, icon, pinned flag and, for a folder, the files it contains one level down (children).
  • list_nodesList nodesGETAgents: ask firstLists the files at the root of a space's working directory (datasheets, folders, forms, dashboards, mirrors): id, name, type, icon, pinned flag. get_node lists a folder's content.
  • search_nodesSearch nodesGETAgents: ask firstSearches the files of a space by type (required) and optionally by name and by the token user's permission, across all folders. Returns id, name, type, icon, parent folder, permission level and pinned flag.

Team, 3 operations

  • create_teamCreate teamPOSTAgents: ask firstCreates a team in a space's contacts, under a parent team when given, with its order and roles. Returns the new team.
  • delete_teamDelete teamDELETEAgents: ask firstDeletes a team from a space's contacts.
  • update_teamUpdate teamPUTAgents: ask firstChanges a team: name, order, parent team and roles. Returns the updated team.

Attachment, 1 operation

  • upload_attachmentUpload attachmentPOSTAgents: ask firstUploads one file to a datasheet's storage and returns its attachment object (name, size, mimeType, storage token, url valid 2 hours). It is not in a record yet: put that object in an Attachment field with create_records or update_records.

Child, 1 operation

  • list_sub_teamsList sub teamsGETAgents: ask firstLists the teams directly under a team, 1 to 1000 per page (default 100): unitId, name, order, parent and roles.

Completion, 1 operation

  • create_chat_completionCreate chat completionPOSTAgents: ask firstSends a conversation to an AITable AI agent and returns its answer (OpenAI-style choices) with token usage and the message credits it cost. Only for accounts AITable has whitelisted; no streaming.

Datasheet, 1 operation

  • create_datasheetCreate datasheetPOSTAgents: ask firstCreates a datasheet in a space, in a folder or at the root, with up to 200 fields (3 default columns when none are given). Returns its id, creation time and the ids of its fields.

Space, 1 operation

  • list_spacesList spacesGETAgents: ask firstLists the spaces the token's user created or was invited to: id, name and whether the user is the space's primary admin. A space id is needed by most other tools.

Unit, 1 operation

  • list_role_unitsList role unitsGETAgents: ask firstLists the members and teams that have a role (members are personal data: name, avatar, status, and with sensitiveData=true email and phone number).

View, 1 operation

  • list_viewsList viewsGETAgents: ask firstLists the views of a datasheet: id, name and type (Grid, Gallery, Kanban or Gantt). A view id narrows list_records and list_fields.

Use AITable from Claude Code, Cursor or Codex

Connect AITable in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its AITable operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect AITable

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect AITable once

    Add your AITable connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

AITable integration FAQ

What can you do with the AITable integration?

LiveContext exposes 31 operations on AITable, covering member, record, role and embedlink.

Popular integrations

Browse the whole catalog