What is Mcp Turso Cloud

mcp-turso-cloud is a Model Context Protocol (MCP) server designed for integrating with Turso databases specifically for Large Language Models (LLMs). It features a two-level authentication system for managing organization-level and database-level operations.

Use cases

Use cases for mcp-turso-cloud include managing databases for applications, querying data for analytical purposes, and implementing machine learning models that require direct access to structured data stored in Turso databases.

How to use

To use mcp-turso-cloud, configure it through your MCP client by adding the necessary environment variables such as TURSO_API_TOKEN, TURSO_ORGANIZATION, and optionally TURSO_DEFAULT_DATABASE. You can then execute various operations like listing databases, creating databases, and executing SQL queries.

Key features

Key features include organization-level operations like listing, creating, and deleting databases, as well as database-level operations such as listing tables, executing SQL queries, and performing vector searches. The two-level authentication system enhances security and management capabilities.

Where to use

mcp-turso-cloud can be utilized in various fields including data management, application development, and machine learning, particularly where integration with Turso databases is required for LLMs.

mcp-turso-cloud

A Model Context Protocol (MCP) server that provides integration with
Turso databases for LLMs. This server implements a two-level
authentication system to handle both organization-level and
database-level operations, making it easy to manage and query Turso
databases directly from LLMs.

Features

🏢 Organization-Level Operations

• List Databases: View all databases in your Turso organization
• Create Database: Create new databases with customizable options
• Delete Database: Remove databases from your organization
• Generate Database Token: Create authentication tokens for
  specific databases

💾 Database-Level Operations

• List Tables: View all tables in a specific database
• Execute Read-Only Query: Run SELECT and PRAGMA queries
  (read-only operations)
• Execute Query: Run potentially destructive SQL queries (INSERT,
  UPDATE, DELETE, etc.)
• Describe Table: Get schema information for database tables
• Vector Search: Perform vector similarity search using SQLite
  vector extensions

⚠️ IMPORTANT: Query Execution Security ⚠️

This server implements a security-focused separation between read-only
and destructive database operations:

• Use execute_read_only_query for SELECT and PRAGMA queries (safe,
  read-only operations)
• Use execute_query for INSERT, UPDATE, DELETE, CREATE, DROP, and
  other operations that modify data

This separation allows for different permission levels and approval
requirements:

• Read-only operations can be auto-approved in many contexts
• Destructive operations can require explicit approval for safety

ALWAYS CAREFULLY READ AND REVIEW SQL QUERIES BEFORE APPROVING
THEM! This is especially critical for destructive operations that
can modify or delete data. Take time to understand what each query
does before allowing it to execute.

Two-Level Authentication System

The server implements a sophisticated authentication system:

1. Organization-Level Authentication

   • Uses a Turso Platform API token
   • Manages databases and organization-level operations
   • Obtained through the Turso dashboard

2. Database-Level Authentication

   • Uses database-specific tokens
   • Generated automatically using the organization token
   • Cached for performance and rotated as needed

Configuration

This server requires configuration through your MCP client. Here are
examples for different environments:

Cline/Claude Desktop Configuration

Add this to your Cline/Claude Desktop MCP settings:

{
  "mcpServers": {
    "mcp-turso-cloud": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-turso-cloud"
      ],
      "env": {
        "TURSO_API_TOKEN": "your-turso-api-token",
        "TURSO_ORGANIZATION": "your-organization-name",
        "TURSO_DEFAULT_DATABASE": "optional-default-database"
      }
    }
  }
}

Claude Desktop with WSL Configuration

For WSL environments, add this to your Claude Desktop configuration:

{
  "mcpServers": {
    "mcp-turso-cloud": {
      "command": "wsl.exe",
      "args": [
        "bash",
        "-c",
        "TURSO_API_TOKEN=your-token TURSO_ORGANIZATION=your-org node /path/to/mcp-turso-cloud/dist/index.js"
      ]
    }
  }
}

Environment Variables

The server requires the following environment variables:

• TURSO_API_TOKEN: Your Turso Platform API token (required)
• TURSO_ORGANIZATION: Your Turso organization name (required)
• TURSO_DEFAULT_DATABASE: Default database to use when none is
  specified (optional)
• TOKEN_EXPIRATION: Expiration time for generated database tokens
  (optional, default: ‘7d’)
• TOKEN_PERMISSION: Permission level for generated tokens (optional,
  default: ‘full-access’)

API

The server implements MCP Tools organized by category:

Organization Tools

list_databases

Lists all databases in your Turso organization.

Parameters: None

Example response:

{
  "databases": [
    {
      "name": "customer_db",
      "id": "abc123",
      "region": "us-east",
      "created_at": "2023-01-15T12:00:00Z"
    },
    {
      "name": "product_db",
      "id": "def456",
      "region": "eu-west",
      "created_at": "2023-02-20T15:30:00Z"
    }
  ]
}

create_database

Creates a new database in your organization.

Parameters:

• name (string, required): Name for the new database
• group (string, optional): Group to assign the database to
• regions (string[], optional): Regions to deploy the database to

Example:

{
  "name": "analytics_db",
  "group": "production",
  "regions": [
    "us-east",
    "eu-west"
  ]
}

delete_database

Deletes a database from your organization.

Parameters:

• name (string, required): Name of the database to delete

Example:

{
  "name": "test_db"
}

generate_database_token

Generates a new token for a specific database.

Parameters:

• database (string, required): Database name
• expiration (string, optional): Token expiration time
• permission (string, optional): Permission level (‘full-access’ or
  ‘read-only’)

Example:

{
  "database": "customer_db",
  "expiration": "30d",
  "permission": "read-only"
}