Connecting Turso & LibSQL Edge Databases to AI Agents using MCP

Connecting Turso & LibSQL Edge Databases to AI Agents using MCP

Turso is an edge database service based on LibSQL, a fork of SQLite optimized for low latency and global distribution. Connecting Turso to an MCP server lets your AI agent execute lightning-fast queries, fetch user analytics, and synchronize changes with edge databases all through natural language prompts.

Prerequisites

1. ▸A Turso (opens in a new tab) account.
2. ▸The Turso CLI installed on your machine.
3. ▸An existing Turso database initialized with data.

Configuration Settings

You can connect your agent directly to the LibSQL edge endpoint using the mcp-server-turso package. Update your MCP configuration:

{
  "mcpServers": {
    "turso": {
      "command": "npx",
      "args": ["-y", "mcp-server-turso"],
      "env": {
        "TURSO_DB_URL": "libsql://my-db-name-my-username.turso.io",
        "TURSO_AUTH_TOKEN": "ts_your_auth_token_here"
      }
    }
  }
}

Note: You can generate the auth token by running turso db tokens create my-db-name in your terminal.

Safe Usage Patterns

When giving an AI agent direct access to an SQL database, safety must be the priority. It is strongly recommended to restrict your agent to strict read-only queries.

Example: Creating a Safe View

Instead of letting the agent query production tables containing PII (personally identifiable information), create a safe SQL view on your database:

-- Safe read-only view creation
CREATE VIEW public_user_analytics AS 
SELECT id, country, signup_date FROM users WHERE status = 'active';

Configure your Turso MCP server connection (using a restricted user or API token) to query only safe views like public_user_analytics rather than raw production tables.

Troubleshooting

• ▸Authentication failed: Check that your TURSO_AUTH_TOKEN is correct. Remember that Turso tokens can be set to expire, so you may need to generate a fresh one.
• ▸Read-only transaction error: If your agent attempts to execute an UPDATE or INSERT but your token only has read permissions, LibSQL will correctly block the transaction. This is intended secure behavior.

Using with OpenAI Codex

There is no install command here on purpose. The package name that used to appear on this page does not exist on the public npm registry, and names in this namespace have been claimed by unrelated parties that now serve placeholder packages. Running npx against an unverified name executes code you did not choose to run.

Before installing any MCP server, check what you are about to execute:

npm view <package-name> version description repository
npm view <package-name> maintainers

If the description and repository do not match what you expect, do not run it. To register a server you have already built or vetted yourself, reference it by absolute path:

codex mcp add --name turso-libsql-mcp --command "node" --args "/absolute/path/to/turso-libsql-mcp/dist/index.js"

Reference: Configuring MCP servers with OpenAI Codex.