Integration

Quickbase integration

Quickbase applications through the RESTful JSON API: query records with the Quickbase query language, insert and update records in one upsert call, delete records by query, read and manage tables and fields, read application properties, and list and run reports. Records are addressed by numeric field id rather than by field name.

Connect Quickbase How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common Quickbase use cases

finding a report id before running it
extending a table before importing extra data
writing collected data into a Quickbase table
finding the key field before writing an upsert
tearing down a scratch table a workflow created
building an application structure from a workflow
removing records a workflow has already processed
checking what a report filters on before running it
reading application variables a workflow depends on
renaming a table created earlier in the same workflow

What you can do with Quickbase

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.

Table, 5 operations

create_tableCreate tablePOSTCreates a table in an application and returns its new table dbid.
delete_tableDelete tableDELETEDeletes a table from an application together with all of its data.
get_tableGet tableGETReturns the properties of a single table, including its key field id.
list_tablesList tablesGETReturns every table of an application, including each table dbid.
update_tableUpdate tablePOSTUpdates a table's name, description or record nouns and returns the new state.

Record, 4 operations

delete_recordsDelete recordsDELETEDeletes every record matching the query and returns how many were removed.
get_records_modified_sinceGet records modified sincePOSTReturns the count, and optionally the ids, of records changed since a timestamp.
query_recordsQuery recordsPOSTReturns records of a table filtered, sorted and grouped as requested.
upsert_recordsUpsert recordsPOSTCreates and updates records in a table and reports which ids were affected.

Field, 3 operations

create_fieldCreate fieldPOSTCreates a field in a table and returns the field id it was given.
get_fieldGet fieldGETReturns one field's type, label and type specific settings.
list_fieldsList fieldsGETReturns every field of a table, which is how you resolve field ids from labels.

Report, 3 operations

get_reportGet reportGETReturns a report's type, description and the query it runs.
list_reportsList reportsGETReturns the reports of a table, so an existing report can be run by id.
run_reportRun reportPOSTRuns a report and returns its rows or aggregated values with paging metadata.

App, 1 operation

get_appGet appGETReturns an application's name, timezone, formats and application variables.

Formula, 1 operation

run_formulaRun formulaPOSTRuns a Quickbase formula and returns its result as a string.

Use Quickbase from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Quickbase once
Add your Quickbase 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.

Quickbase integration FAQ

What can you do with the Quickbase integration?

LiveContext exposes 17 operations on Quickbase, covering table, record, field and report. Common uses include finding a report id before running it, extending a table before importing extra data and writing collected data into a Quickbase table.