Integration

Turso integration

SQLite at the edge with libSQL. Globally replicated databases with low-latency access, embedded replicas, and branching. Perfect for edge computing, serverless applications, and mobile apps requiring local-first databases.

Connect Turso How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common Turso use cases

Cleanup
Region setup
Connection info
Region planning
Application auth
Usage monitoring
Replica monitoring
Database management
Geographic expansion
Database provisioning

What you can do with Turso

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.

Database, 4 operations

create_databaseCreate databasePOSTCreates a new Turso database.
delete_databaseDelete databaseDELETEDeletes a Turso database permanently.
get_databaseGet databaseGETRetrieves database details and configuration.
list_databasesList databasesGETLists all databases in an organization.

Group, 2 operations

create_groupCreate groupPOSTCreates a new location group.
list_groupsList groupsGETLists all location groups in an organization.

Instance, 1 operation

list_instancesList instancesGETLists all instances (replicas) of a database.

Location, 1 operation

add_locationAdd locationPOSTAdds a replica location to a group.

Token, 1 operation

create_tokenCreate tokenPOSTCreates an authentication token for database access.

Usage, 1 operation

get_usageGet usageGETRetrieves usage statistics for a database.

Use Turso from Claude Code, Cursor or Codex

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

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

Turso integration FAQ

What can you do with the Turso integration?

LiveContext exposes 10 operations on Turso, covering database, group, instance and location. Common uses include Cleanup, Region setup and Connection info.