MCP server for integrating Turso with LLMs
MCP server for integrating Turso with LLMs. Exposed over MCP by the mcp turso cloud mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
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.
Everything the assistant can do here goes through one of these:
list_databases — The list_databases tool exposed by this servercreate_database — The create_database tool exposed by this serverdelete_database — The delete_database tool exposed by this servergenerate_database_token — The generate_database_token tool exposed by this serverlist_tables — The list_tables tool exposed by this serverexecute_read_only_query — Executes a read-only SQL query (SELECT, PRAGMA) against a databaseexecute_query — Executes a potentially destructive SQL query (INSERT, UPDATE, DELETE, CREATE, etc.) against a databasedescribe_table — The describe_table tool exposed by this servervector_search — Performs vector similarity search using SQLite vector extensionsSetup — The Setup tool exposed by this serverPublishing — The Publishing tool exposed by this serverYou will need 3 environment variables: TURSO_API_TOKEN, TURSO_ORGANIZATION, TURSO_DEFAULT_DATABASE. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Turso Cloud's toolset — list_databases, create_database, delete_database and 8 more — is a fair guide to whether it matches your workflow. It is maintained by spences10; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Turso Cloud's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_databases | The list_databases tool exposed by this server. |
| create_database | The create_database tool exposed by this server. |
| delete_database | The delete_database tool exposed by this server. |
| generate_database_token | The generate_database_token tool exposed by this server. |
| list_tables | The list_tables tool exposed by this server. |
| execute_read_only_query | Executes a read-only SQL query (SELECT, PRAGMA) against a database. |
| execute_query | Executes a potentially destructive SQL query (INSERT, UPDATE, DELETE, CREATE, etc.) against a database. |
| describe_table | The describe_table tool exposed by this server. |
| vector_search | Performs vector similarity search using SQLite vector extensions. |
| Setup | The Setup tool exposed by this server. |
| Publishing | The Publishing tool exposed by this server. |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TURSO_API_TOKEN | Credential the server authenticates with. | Yes |
| TURSO_ORGANIZATION | Configuration value read at startup. | Optional |
| TURSO_DEFAULT_DATABASE | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.