Skip to content

Summary

Turso's hosted MCP server — manage Turso Cloud databases, branch them point-in-time and run SQL from a coding agent, authorised over OAuth with no API token to paste.

Features

  • Hosted remote server at https://mcp.turso.ai/mcp — nothing to self-host
  • OAuth 2.1 + PKCE login with org- and group-scoped consent, no API token
  • List, inspect, create, delete and branch Turso Cloud databases
  • Point-in-time database branching for reproducing past state
  • Read, write, delete and schema-change SQL split into separate least-privilege tools
  • Per-database query analytics: top queries by frequency and latency
  • Update delete-protection, IP/VPC allow rules and size limits
  • Claude Code and Cursor plugin marketplace install

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Turso MCP Server" tools will be available.
{
  "mcpServers": {
    "turso-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.turso.ai/mcp"
      ]
    }
  }
}

Description

Turso's official Model Context Protocol server connects an AI agent to Turso Cloud, the managed SQLite/libSQL platform. It is a hosted remote server at https://mcp.turso.ai/mcp — there is nothing to run locally and no long-lived credential to copy into a config file.

OAuth instead of an API token. Authorisation is OAuth 2.1 with PKCE, discovered from the server itself per RFC 9728. You approve the connection in the browser — picking the organisation, and optionally a single group, that the agent may touch — and the client receives a scoped token. That is a meaningfully different security posture from the usual pattern of pasting a platform-wide API key into mcp.json.

What the agent can do. Databases: list, inspect, create, delete, and branch — including point-in-time branches, so an agent can fork production as of an hour ago to reproduce a bug. Configuration: delete-protection, IP and VPC allow rules, and size limits. SQL: read-only queries, writes, deletes, and schema changes are each exposed as a separate tool rather than one execute_sql, so an agent reaching for a read is not holding a tool that can drop a table, and a client that surfaces destructive-operation warnings can act on the annotation. Analytics: per-database insight into the top queries by frequency and latency.

Getting connected. Claude Code installs it as a plugin (/plugin marketplace add tursodatabase/turso-mcp, then /plugin install turso@turso); Cursor takes the same marketplace URL, a one-click deeplink, or a three-line entry in ~/.cursor/mcp.json; Claude web and desktop add it under Settings → Connectors as a custom connector. Any other MCP client can simply be pointed at the endpoint and will discover the OAuth flow on its own.

The plugin wrapper is MIT-licensed and published by the Turso team at tursodatabase/turso-mcp.

Related MCP Servers

New

InfluxData's official MCP server for InfluxDB 3 — schema discovery, bounded SQL and InfluxQL queries, line-protocol writes and token administration across Core, Enterprise and Cloud.

New

Mixpanel's official hosted MCP server — 80+ tools for querying product analytics, building boards, managing cohorts and metrics, and reading session replays.

MCP: Tableau MCP

by Tableau

Featured

Tableau's own MCP server — query published data sources, explore workbooks and views, and render live vizzes inside an AI client.

Browse all MCP servers →