Integration

MotherDuck integration

MotherDuck administration API. Create and delete service accounts, mint, list and revoke their access tokens, read and change the compute size, replica count and cooldown of their ducklings, see which accounts are currently running compute, and mint an embed session for a Dive dashboard. This is the control plane only: SQL is not available over HTTP, it runs through a DuckDB client attached with a token or through the PostgreSQL wire endpoint, so no call here reads or writes table data. MotherDuck labels this API a preview and its shape may still change.

Connect MotherDuck How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common MotherDuck use cases

issuing a short lived token for a CI job
auditing which tokens exist for a service account
provisioning a dedicated account for a scheduled job
raising the instance size before a heavy nightly load
rotating a leaked token after issuing its replacement
embedding a customer facing dashboard in a product page
checking the compute size of an account before raising it
seeing which service accounts are burning compute right now
removing a service account after decommissioning the job that used it
finding tokens that are about to expire

What you can do with MotherDuck

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.

Access token, 3 operations

create_access_tokenCreate access tokenPOSTMints an access token for an account and returns the secret once.
delete_access_tokenDelete access tokenDELETEInvalidates one access token of an account.
list_access_tokensList access tokensGETLists the tokens of an account with their type and expiry, without the secrets.

Duckling, 2 operations

get_duckling_configGet duckling configGETReturns the instance size, replica count and cooldown of an account's compute.
set_duckling_configSet duckling configPUTChanges the instance size, replica count and cooldown of an account's compute.

Service account, 2 operations

create_service_accountCreate service accountPOSTCreates a service account user that tokens can then be minted for.
delete_service_accountDelete service accountDELETEPermanently deletes a user and everything it owns.

Active account, 1 operation

list_active_accountsList active accountsGETLists the accounts with a running or cooling down duckling.

Embed session, 1 operation

create_dive_embed_sessionCreate dive embed sessionPOSTMints a short lived session that lets an application embed a Dive dashboard for a service account.

Use MotherDuck from Claude Code, Cursor or Codex

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

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

MotherDuck integration FAQ

What can you do with the MotherDuck integration?

LiveContext exposes 9 operations on MotherDuck, covering access token, duckling, service account and active account. Common uses include issuing a short lived token for a CI job, auditing which tokens exist for a service account and provisioning a dedicated account for a scheduled job.