Skip to content

Start building

Integration · Databases

AI agents for Turso

Query and change a Turso (libSQL, SQLite-compatible) database over its HTTP API: run SQL with bound parameters, list its tables and columns, and apply several changes as one transaction, with a database auth token.

Actions
6
Read
3
Write
3

Actions

What your agents can do in Turso

6 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 3

Look things up. Nothing changes.

  • Run a SQL query

    Runs one read-only SQLite statement (SELECT or EXPLAIN; one statement, no semicolons inside) and returns its rows.

  • List tables

    Lists the database's tables and views with the statement that created each one (which shows its columns, keys and constraints), from sqlite_master.

  • Describe a table

    Lists a table's columns: each column's position, name, declared type, whether it is NOT NULL, its default and its place in the primary key (0 when not part of it), from pragma_table_info.

Write 3

Create, change or send.

  • Insert, update or create

    Runs one statement that adds or changes data: INSERT (including INSERT OR REPLACE and ON CONFLICT upserts), UPDATE, REPLACE, or CREATE (a table, index, view or trigger).

  • Apply changes as one transaction

    Runs up to 10 statements in order inside one transaction (BEGIN, the statements, COMMIT).

  • Run any SQL statementDeletes data

    Runs any one SQLite statement, including DELETE, DROP, ALTER and anything else the token is allowed to do: this is the action that can remove data, and it cannot be undone.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Turso account.

What you enter

  • Database auth token

Settings

  • Database URL

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Turso data

    Ask a question in plain words. The agent can run a SQL query, list tables or describe a table in Turso, then answers with what it found.

  • 02

    Let an agent update Turso

    Have the agent insert, update or create or run any SQL statement in Turso as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Turso and Slack: it can run a SQL query in Turso and post a summary to a Slack channel in the same run.

FAQ

Turso and MyDeepAgents

Can MyDeepAgents connect to Turso?

Yes. The Turso connector has 6 actions: 3 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Turso?

Paste an API key from your Turso account. You'll need: Database auth token. The connection also asks for: Database URL. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Turso without asking?

Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.

Can I use Turso in workflows as well as agents?

Yes. Every Turso action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Turso to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.