Turso MCP Server for Claude
Connect Claude to a local or in-memory Turso/libSQL database — query, insert, update, delete, and manage schemas with nine dedicated tools — using the official MCP server built into the Turso CLI with the `--mcp` flag.
Open the source and read safety notes before installing.
Safety notes
- The MCP server exposes full read and write access to the connected database — Claude can INSERT, UPDATE, DELETE, and ALTER TABLE.
- Test with a development or in-memory database before connecting to a database with production data.
- The `schema_change` tool (CREATE, ALTER, DROP) is available — review schema-modifying operations before executing.
Privacy notes
- All table contents, row data, and schema definitions are surfaced in Claude's context when queries are run.
- Treat database files as sensitive if they contain personal or confidential data.
Prerequisites
- Turso CLI installed: `brew install tursodatabase/tap/turso` or from turso.tech/docs/cli/installation.
- A Turso/libSQL database file, or use `tursodb --mcp` for an ephemeral in-memory database.
- An MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 5 minutes
- Difficulty
- beginner
- Website
- https://turso.tech
Full copyable content
{
"mcpServers": {
"my-database": {
"command": "tursodb",
"args": ["./path/to/database.db", "--mcp"]
}
}
}About this resource
Overview
The Turso MCP Server is the official Model Context Protocol integration built into the Turso
CLI. Running tursodb <database.db> --mcp starts a local stdio MCP server that gives Claude nine
tools for working with any Turso/libSQL (SQLite-compatible) database — queries, inserts, updates,
deletes, and schema management — all through natural language.
For quick prototyping without a file, tursodb --mcp creates an ephemeral in-memory database.
Key capabilities
Nine tools are exposed:
open_database— open a different database file.current_database— describe the currently connected database.list_tables— list all tables in the database.describe_table— get the schema of a specific table.execute_query— run a read-onlySELECTquery.insert_data— insert new rows into a table.update_data— update existing rows.delete_data— delete rows from a table.schema_change— executeCREATE,ALTER, orDROPDDL statements.
How it compares
| Server | Local SQLite/libSQL | In-memory option | Full CRUD | Schema changes | Transport |
|---|---|---|---|---|---|
| Turso MCP | Yes (libSQL) | Yes | Yes | Yes | stdio |
| SQLite MCP (generic) | Yes | No | Yes | Yes | stdio |
| MotherDuck MCP | No (DuckDB/cloud) | No | Yes | Yes | stdio |
| PlanetScale MCP | No (MySQL/cloud) | No | Limited | No | Remote HTTP |
Turso's MCP is unique in being the only official libSQL/SQLite-compatible MCP server with in-memory database support — ideal for rapid prototyping and testing AI-driven database workflows.
Installation
Claude Code
# Connect to a database file
claude mcp add my-database -- tursodb ./my-app.db --mcp
# Or use an in-memory database
claude mcp add in-memory-db -- tursodb --mcp
Claude Desktop
{
"mcpServers": {
"my-database": {
"command": "tursodb",
"args": ["./path/to/database.db", "--mcp"]
}
}
}
Multiple databases
Add multiple MCP entries with different names and database paths to switch between databases.
Requirements
- Turso CLI (install via
brew install tursodatabase/tap/tursoor from turso.tech). - A Turso/libSQL database file (or use in-memory mode).
- An MCP client (Claude Code or Claude Desktop).
Security
- Provide only the minimum database access Claude needs; use a read-only database copy if write operations are not required.
- In-memory databases are ephemeral — they do not persist after the MCP server exits.
- Never connect the MCP server to a database containing production credentials or sensitive PII without appropriate access controls.
Source Verification Notes
Verified on 2026-06-18:
- The official Turso repository
github.com/tursodatabase/tursois the authoritative source for thetursodb --mcpcommand and the built-in MCP server. - Turso's MCP documentation at
docs.turso.tech/agentfs/guides/mcpdocuments the Claude Code installation command, in-memory database option, and the nine tool categories. - Turso's blog announcement describes the
--mcpflag behavior and Claude integration pattern. - Claude Code's MCP documentation describes the
--separator pattern used above.
Source citations
Add this badge to your README
How it compares
Turso MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Turso MCP Server for Claude Connect Claude to a local or in-memory Turso/libSQL database — query, insert, update, delete, and manage schemas with nine dedicated tools — using the official MCP server built into the Turso CLI with the `--mcp` flag. Open dossier | MCP SQLite Server for Claude Read and write any local SQLite database from Claude — get database info, list tables, inspect schemas, create/read/update/delete records, and run raw SQL queries — with the MCP SQLite server that connects to any `.db` file you specify. Open dossier | DBHub MCP Server Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, and SQLite. Open dossier | MCP Toolbox for Databases Open source MCP server and tool framework from Google for connecting AI agents, IDEs, and applications to databases through prebuilt or custom database tools. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Turso | jparkerweb | Bytebase | |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-05 | 2026-06-05 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓The MCP server exposes full read and write access to the connected database — Claude can INSERT, UPDATE, DELETE, and ALTER TABLE. Test with a development or in-memory database before connecting to a database with production data. The `schema_change` tool (CREATE, ALTER, DROP) is available — review schema-modifying operations before executing. | ✓The `query` tool executes arbitrary SQL including INSERT, UPDATE, and DELETE statements — it is not read-only. Point the server at a copy or test database to avoid accidental data loss before trusting it with production data. | ✓DBHub can execute SQL queries against configured databases. SQL execution can read, create, update, delete, or otherwise modify data depending on database permissions and requested queries. Configure read-only mode, row limits, query timeouts, least-privilege credentials, and human review before using DBHub with production or sensitive databases. Custom tools can wrap reusable parameterized SQL, so review their definitions before allowing agents to call them. | ✓Database tools can expose sensitive schemas and data, and some custom tools can modify data if configured that way. Prefer least-privilege accounts, read-only roles for exploration, query limits, and approved toolsets. Review every `tools.yaml` statement, parameter, source, and toolset before giving it to an agent. Avoid broad `execute_sql` access in production; expose structured, parameterized tools where possible. Query loops can create high database load, unexpected cloud costs, lock contention, or noisy audit logs. |
| Privacy notes | ✓All table contents, row data, and schema definitions are surfaced in Claude's context when queries are run. Treat database files as sensitive if they contain personal or confidential data. | ✓All database content including table schemas, record data, and query results are surfaced in Claude's context — do not connect databases containing sensitive personal or credential data unless you intend to share it with the model. No credentials are required and no data is sent to external services — the server operates entirely locally. | ✓Database connection strings, hostnames, schemas, table names, column names, row data, query text, query results, traces, and errors may be visible to the MCP client and model provider. Databases can contain personal data, customer records, credentials, business metrics, audit logs, payment data, healthcare data, and proprietary operational state. Avoid exposing production databases or regulated data unless the database, MCP client, and model session are approved for that access. | ✓Schema names, table names, query text, query results, connection metadata, and business data may pass through the MCP server and AI client. Database passwords, IAM credentials, service account keys, and connection strings are secrets and should never be committed or pasted into prompts. Logs, traces, and metrics can include tool names, query metadata, error messages, and database identifiers. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Featured in
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.