Integration

Bubble integration

A Bubble application's own Data API and Workflow API: search, read, create, modify, replace and delete things in the app database, and trigger a backend API workflow. The endpoints belong to one Bubble app, so the app domain and the API token are part of the connection, and the app must have the Data API or Workflow API switched on for the types and workflows you address.

Connect Bubble How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common Bubble use cases

re-reading a record after modifying it
writing collected data into a Bubble app database
removing a record a workflow has already processed
running app side logic that the Data API cannot express
rewriting a record wholesale from an authoritative source
reading the records of a Bubble app that match a condition
writing a computed status back onto an existing Bubble record
paging through a Bubble data type
handing work to a Bubble backend workflow from an external process

What you can do with Bubble

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.

Thing, 6 operations

create_thingCreate thingPOSTCreates a thing and returns the unique id Bubble assigned to it.
delete_thingDelete thingDELETEDeletes a single thing from the app database.
get_thingGet thingGETReturns a single thing, addressed by the unique id Bubble assigned it.
modify_thingModify thingPATCHUpdates only the fields you send on an existing thing.
replace_thingReplace thingPUTOverwrites a thing with the body you send, discarding the fields you omit.
search_thingsSearch thingsGETReturns the things of one data type that match the constraints.

Workflow, 1 operation

trigger_workflowTrigger workflowPOSTRuns a backend API workflow of the Bubble app and returns whatever it returns.

Use Bubble from Claude Code, Cursor or Codex

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

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

Bubble integration FAQ

What can you do with the Bubble integration?

LiveContext exposes 7 operations on Bubble, covering thing and workflow. Common uses include re-reading a record after modifying it, writing collected data into a Bubble app database and removing a record a workflow has already processed.