Navigation
MCP-Turso: Secure Access & Precision Control - MCP Implementation

MCP-Turso: Secure Access & Precision Control

MCP-Turso empowers LLMs with secure, seamless Turso database access via dual-layer auth—manage org-wide and per-database ops effortlessly. Query and control with precision." )

Developer Tools
4.6(160 reviews)
240 saves
112 comments

This tool saved users approximately 14341 hours last month!

About MCP-Turso

What is MCP-Turso: Secure Access & Precision Control?

MCP-Turso is a specialized server built on the Model Context Protocol (MCP) framework, designed to integrate Turso databases with large language models (LLMs). It introduces a robust two-tier authentication system to manage organization-wide and database-specific operations, enabling seamless and secure database administration directly from LLM workflows. This tool simplifies tasks like creating, querying, and securing databases while maintaining strict access controls.

How to Use MCP-Turso: Secure Access & Precision Control?

Configuration depends on your environment:

  • Cline Setup: Add the MCP server configuration with Turso API token, organization name, and optional defaults in your settings.
  • WSL Integration: Configure Claude Desktop with a WSL command script pointing to your MCP-Turso instance.
  • Environment Variables: Set mandatory `TURSO_API_TOKEN` and `TURSO_ORGANIZATION`, plus optional parameters like token expiration or permissions.

Refer to the provided JSON snippets for exact syntax and paths.

MCP-Turso Features

Key Features of MCP-Turso: Secure Access & Precision Control

Two core systems power its capabilities:

Authentication Hierarchy

  • Organization-Level: Uses Turso API tokens for high-level database management and token generation.
  • Database-Level: Auto-generated per-database tokens with caching and rotation, ensuring granular access control.

Operational Flexibility

  • Execute SQL queries and vector searches with SQLite extensions.
  • Generate descriptive table schemas and manage database lifecycles (create/delete).
  • Automate workflows through API endpoints like generate_database_token and execute_query.

Use Cases of MCP-Turso: Secure Access & Precision Control

Common scenarios include:

  • Multi-Database Management: Streamline operations across an organization’s entire database inventory.
  • Real-Time Analytics: Query live data or perform vector similarity searches for recommendation systems.
  • Permission Auditing: Temporarily grant restricted access via short-lived tokens without exposing API keys.
  • CI/CD Automation: Embed database provisioning into deployment pipelines using MCP tooling.

MCP-Turso FAQ

FAQ from MCP-Turso: Secure Access & Precision Control

Q: Why use two authentication layers?
The dual system isolates risks: organization tokens handle administrative tasks, while database-specific tokens limit exposure for end-user operations.

Q: How do I troubleshoot connection failures?
1. Validate API token permissions and organization name.
2. Confirm database existence via list_databases.
3. Check for typos in database names or region configurations.

Q: Can I customize token expiration?
Yes! Set TOKEN_EXPIRATION (default 7 days) or override per-token with expiration parameter.

Q: What SQL features are supported?
Full SQL syntax including vector operations via SQLite’s R_tree extensions for similarity searches.

Content

mcp-turso

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.

Glama badge

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 Query : Run SQL queries against your databases
  • Describe Table : Get schema information for database tables
  • Vector Search : Perform vector similarity search using SQLite vector extensions

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
  1. 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 Configuration

Add this to your Cline MCP settings:

{
  "mcpServers": {
    "mcp-turso": {
      "command": "node",
      "args": ["/path/to/mcp-turso/dist/index.js"],
      "env": {
        "TURSO_API_TOKEN": "your-turso-api-token",
        "TURSO_ORGANIZATION": "your-organization-name",
        "TURSO_DEFAULT_DATABASE": "optional-default-database"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Claude Desktop with WSL Configuration

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

{
  "mcpServers": {
    "mcp-turso": {
      "command": "wsl.exe",
      "args": [
        "bash",
        "-c",
        "TURSO_API_TOKEN=your-token TURSO_ORGANIZATION=your-org node /path/to/mcp-turso/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"
}

Database Tools

list_tables

Lists all tables in a database.

Parameters:

  • database (string, optional): Database name (uses context if not provided)

Example:

{
  "database": "customer_db"
}

execute_query

Executes a SQL query against a database.

Parameters:

  • query (string, required): SQL query to execute
  • params (object, optional): Query parameters
  • database (string, optional): Database name (uses context if not provided)

Example:

{
  "query": "SELECT * FROM users WHERE age > ?",
  "params": { "1": 21 },
  "database": "customer_db"
}

describe_table

Gets schema information for a table.

Parameters:

  • table (string, required): Table name
  • database (string, optional): Database name (uses context if not provided)

Example:

{
  "table": "users",
  "database": "customer_db"
}

vector_search

Performs vector similarity search using SQLite vector extensions.

Parameters:

  • table (string, required): Table name
  • vector_column (string, required): Column containing vectors
  • query_vector (number[], required): Query vector for similarity search
  • limit (number, optional): Maximum number of results (default: 10)
  • database (string, optional): Database name (uses context if not provided)

Example:

{
  "table": "embeddings",
  "vector_column": "embedding",
  "query_vector": [0.1, 0.2, 0.3, 0.4],
  "limit": 5,
  "database": "vector_db"
}

Development

Setup

  1. Clone the repository
  2. Install dependencies:
npm install
  1. Build the project:
npm run build
  1. Run in development mode:
npm run dev

Publishing

  1. Update version in package.json
  2. Build the project:
npm run build
  1. Publish to npm:
npm publish

Troubleshooting

API Token Issues

If you encounter authentication errors:

  1. Verify your Turso API token is valid and has the necessary permissions
  2. Check that your organization name is correct
  3. Ensure your token hasn't expired

Database Connection Issues

If you have trouble connecting to databases:

  1. Verify the database exists in your organization
  2. Check that your API token has access to the database
  3. Ensure the database name is spelled correctly

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License - see the LICENSE file for details.

Acknowledgments

Built on:

Related MCP Servers & Clients