How to connect Turso to Claude

Connect Claude Web, Desktop and Cowork to Turso MCP. Find the closest turso region to berlin, stream real-time updates from the orders table, and more using natural language, with authentication handled for you.

Turso logoTurso
Api Key

Turso is a fully managed database platform built on libSQL, delivering serverless SQLite databases with global replication. It's perfect for applications needing fast, low-latency data access across regions.

3 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Turso account to Claude via Composio Connect, enabling it to find the closest Turso region to Berlin, stream real-time updates from the orders table, check if your API token is still valid, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Turso with

Connecting Turso to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Turso account

Back in Claude, ask it to connect to Turso or give it any Turso-related task.

For example, ask Claude to:

  • "Find the closest Turso region to Berlin"
  • "Stream real-time updates from the orders table"
  • "Check if your API token is still valid"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Turso account is ready to use.

What is the Turso Claude Connector, and what's possible with it?

The Turso MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Turso account. It provides structured and secure access to your Turso databases, so your agent can discover optimal regions, monitor real-time table changes, and validate API tokens for secure automation on your behalf.

  • Region optimization for deployments: Instantly find and select the closest Turso region to minimize database latency based on your agent’s or application’s location.
  • Real-time change monitoring: Let your agent listen for real-time insert, update, or delete operations on specific tables, enabling immediate reactions to critical data changes.
  • API token validation: Have your agent check and confirm the validity and expiration time of Turso API tokens before running sensitive operations.
  • Event-driven automation: Build workflows that automatically trigger downstream actions in response to live database updates streamed via Turso’s change listener.

Troubleshooting

1. Why does Claude not use the Composio connector for Turso?

The connector can show as connected, but Claude must use it in each Turso conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Turso again.

2. Why does Claude show an MCP server error before Turso connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Turso.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Turso.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Turso authorization link not work?

The Composio connector is one server. Your Turso account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Turso connection.
  • Composio creates a fresh Turso authorization link.
  • Open that link in your browser and finish the Turso sign-in.

4. Why do Turso actions fail after they worked before?

The Turso connection can expire or lose permission.

  • Ask Claude to inspect the Turso connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Turso account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Turso.
  • If the action still fails with a permission error, check that the connected account has that permission in Turso itself.

5. How do I switch to a different Turso account?

Claude can manage the Turso connection for you.

  • Ask Claude to disconnect or delete the current Turso account.
  • Ask Claude to connect Turso again.
  • Open the new Composio authorization link for Turso.
  • Sign in with the other Turso account in the browser.
  • After the account connects, ask Claude to retry the Turso task.

6. Why is my Turso connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Turso connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If Turso tools still do not appear, click , disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Turso.
TOOLS

Supported Tools

Every Turso action and event your agent gets out of the box.

Closest Region

Tool to get the closest Turso region based on client location.

Listen To Changes

Listen to committed table changes in a Turso database via the /beta/listen endpoint.

Validate API Token

Validates a Turso API token and retrieves its expiration time.

FAQ

Frequently asked questions

With a standalone Turso MCP server, the agents and LLMs can only access a fixed set of Turso tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Turso and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Turso tools.

Yes, absolutely. You can configure which Turso scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Turso data and credentials are handled as safely as possible.

Start with Turso.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Turso tool your agent needs.Free to start.

Start building