Integration

Glide integration

Glide builds no-code apps on top of data tables; this is the Glide API v2.0 (public beta), which works with Glide Big Tables only. An agent can list the team's Big Tables, create a table with an optional schema and initial rows, overwrite a table's rows (and optionally its schema), read rows page by page or one by one, add rows, update or delete a single row, and check an asynchronous job. Adding, updating or deleting rows uses 0.01 Glide update per row changed and reading uses 0.001 per row, billed against the team's quota. Not exposed: stashing (chunked uploads for datasets over 15 MB), CSV or TSV bodies, file uploads (they need the bytes sent to a pre-signed storage URL), the row-version check and If-Match versioning, and the import-from-URL route the reference pages do not document. Authentication is a Glide user's API token, found in the Glide Data Editor and sent as a Bearer token; it is scoped to that user's team and reaches every app and table in it.

Connect Glide How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Glide

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.

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

Row, 5 operations

add_rowsAdd rowsPOSTAppends one or more rows to an existing Big Table and returns their row ids in input order. Columns left out stay empty. Uses 0.01 Glide update per row added.
delete_rowDelete rowDELETEDeletes one row from a Big Table. Answers success also when the row does not exist. Uses 0.01 Glide update.
get_rowGet rowGETReturns one row of a Big Table by its row id, as an object keyed by column id. Contains whatever the table stores.
list_rowsList rowsGETReturns rows of a Big Table, one page at a time: each row is an object keyed by column id, with its row id in $rowID. When continuation is set in the answer, call again with it for the next page. Contains whatever the table stores.
update_rowUpdate rowPATCHUpdates the given columns of one row in a Big Table; columns left out keep their value. Uses 0.01 Glide update.

Table, 3 operations

create_tableCreate tablePOSTCreates a new Big Table with a name, an optional column schema (inferred from the rows when omitted) and its initial rows (an empty list creates an empty table). Returns the table id and the ids of the added rows, in input order.
list_tablesList tablesGETLists every Big Table of the team the API token belongs to, with each table's id and name. Tables of other kinds in the team are not included.
overwrite_tableOverwrite tablePUTOverwrites a Big Table: deletes every existing row, then adds the given rows, optionally replacing the column schema. Destructive: send an empty rows list to clear the table. User-specific columns are cleared too.

Job, 1 operation

get_jobGet jobGETReturns the status of an asynchronous job started by create_table or overwrite_table (running, succeeded or failed), its result once it succeeded and its error message if it failed.

Use Glide from Claude Code, Cursor or Codex

Connect Glide in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Glide 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 Glide

Create your workspace
Sign up free. Nothing to install.
Connect Glide once
Add your Glide connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.