Skip to main content
Turso runs a hosted Model Context Protocol (MCP) server at https://mcp.turso.ai/mcp. Connect any MCP-capable AI agent and it can manage your Turso Cloud account — organizations, databases, groups — and run SQL, on your behalf. Authentication is OAuth 2.1 (the same model you use to log in to the dashboard): you approve access in the browser and the agent receives a scoped token. There’s no API token to copy or paste.

​
What the agent can do

Once connected, the agent has tools to:
  • Databases — list, inspect, create, delete, and branch databases (including point-in-time branches), and update configuration (delete-protection, IP/VPC allow rules, size limits).
  • SQL — run read-only queries, writes, deletes, and schema changes, each as a separate tool so the agent uses the least-powerful one for the task.
  • Insight — per-database analytics (top queries by frequency and latency).
Read-only and destructive operations are labeled, so the agent can tell them apart and confirm before doing anything that changes data.

​
Connect

Install the plugin, then authenticate:
/plugin marketplace add tursodatabase/turso-mcp
/plugin install turso@turso
Run /mcp, select turso, and choose Authenticate. Your browser opens to approve access (see Authorize below).

​
Authorize access

When the browser opens, you’ll log in to Turso (if you aren’t already) and land on a consent screen where you choose what the agent can access:
  • the organization;
  • optionally a single group to limit the token to — or the whole organization for full access;
  • for a group, the permissions (read-only, full-access, or a custom set).
Approve, and the agent is connected. To re-scope or switch organizations, disconnect and authenticate again (in Claude Code: /mcp → turso → Clear authentication).
Picking a group scopes the token to that group’s resources — the least-privilege choice. “Entire organization” grants full access. Either way the token is enforced at Turso’s API: every tool call is checked for org-binding, role, and scope, and recorded in your audit log.

​
How it works

  • The MCP server holds no privilege of its own. Each tool forwards your request to the regular Turso platform API carrying your token, so the same authorization and audit rules apply as any other API access.
  • The token is organization- or group-scoped; unscoped tokens are rejected.
  • Consent happens on the Turso dashboard — the only place that can see your login session — which mints the scoped token the agent then uses.

​
Resources