MCP Turso

🚀 MCP-Turso Server

An MCP (Model Context Protocol) server that provides access to LibSQL databases hosted on Turso. Currently, the server offers the following features:

• Retrieve the list of tables in the database.
• Obtain the database schema.
• Get the schema of a specific table.
• Execute SELECT queries.

🚀 Quick Start

Configuration

Using Claude Desktop

Add the following content to your claude_desktop_config.json file:

{
   "mcpServers": {
      "turso": {
         "command": "npx",
         "args": ["-y", "mcp-turso"],
         "env": {
            "TURSO_DATABASE_URL": "Your database URL",
            "TURSO_AUTH_TOKEN": "Your authentication token"
         }
      }
   }
}

You need an existing database to proceed. If you don't have one, you can create one. To get the database URL via the Turso CLI, run:

turso db show --url <database-name>

Then, obtain the authentication token for the database:

turso db tokens create <database-name>

Add these values to the above configuration.

Using Cursor

To configure the Turso MCP server in Cursor, follow these steps:

1. Open Cursor, go to Settings (⚙️) > Settings (JSON).
2. Add the following configuration to your settings JSON file:

"mcpServers": {
  "turso": {
    "command": "npx",
    "args": ["-y", "mcp-turso"],
    "env": {
      "TURSO_DATABASE_URL": "Your database URL",
      "TURSO_AUTH_TOKEN": "Your authentication token"
    }
  }
}

Replace your_url and your_token with your Turso database URL and authentication token, as described above.

Logging

The server includes a custom logger for debugging outside of Claude Desktop. By default, this logger writes to <parent-dir>/logs/mcp-turso.log, where <parent-dir> is the parent directory of the directory containing the mcp-turso script. For example, if the path to mcp-turso is ~/foo/bin/mcp-turso, the log file is located at ~/foo/logs/mcp-turso.log. If you run it using the above NPX configuration, the default log location is:

~/.npm/_npx/<npx-dir-name>/node_modules/mcp-turso/logs/mcp-turso.log

You can set a custom log path by specifying an absolute POSIX path, but currently, Windows systems are not fully supported.

✨ Features

Feature List

• list_tables: Retrieve the list of tables in the database.
• get_db_schema: Obtain the schema of the entire database.
• describe_table: Get the schema of a specific table.
• query_database: Execute an arbitrary SELECT query and return the results.

Input and Output Description

list_tables

Input: None
Output: A list containing all table names.

get_db_schema

Input: None
Output: The schema information of the entire database, including tables, columns, and other structures.

describe_table

Input: Table name
Output: Detailed schema information of the specified table, including column names, data types, etc.

query_database

Input: SQL query statement
Output: The query result set, usually returned in tabular form.

📋 To-Do List

• Support the logging function on Windows systems.
• Add support for more database operations.