What distinguishes read-only from destructive queries?
The server provides separate tools: `execute_read_only_query` for SELECT/PRAGMA (safe, can be auto-approved) and `execute_query` for INSERT/UPDATE/DELETE/CREATE (requires explicit approval).
@spences10
Basic information
🗂️ 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
Add this server to your MCP-compatible client using the configuration below.
{
"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": []
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
mcp-turso is a Model Context Protocol (MCP) server that integrates Turso databases with LLMs, using a two-level authentication system to manage organization-level and database-level operations directly from LLMs.
Configure the server in your MCP client (e.g., Cline or Claude Desktop) by setting the required environment variables TURSO_API_TOKEN and TURSO_ORGANIZATION, and optionally TURSO_DEFAULT_DATABASE. Run with npx -y mcp-turso-cloud. Invoke tools like list_databases, create_database, execute_read_only_query, or vector_search via the LLM.
describe_table toolThe server provides separate tools: `execute_read_only_query` for SELECT/PRAGMA (safe, can be auto-approved) and `execute_query` for INSERT/UPDATE/DELETE/CREATE (requires explicit approval).
`TURSO_API_TOKEN` (Turso Platform API token) and `TURSO_ORGANIZATION` (organization name) are required. `TURSO_DEFAULT_DATABASE`, `TOKEN_EXPIRATION` (default '7d'), and `TOKEN_PERMISSION` (default 'full-access') are optional.
Database tokens are generated automatically using the organization token, cached for performance, and rotated as needed. Their expiration and permissions can be configured via environment variables.
The server uses standard MCP tool-based transport (stdio via `npx`), authenticating via the Turso Platform API token for organization-level actions and database-specific tokens for database-level operations.
The server depends on the @libsql/client and Turso’s API. It runs via Node.js and requires network access to Turso. No other runtime dependencies are mentioned.
The Xata MCP server lets AI assistants and agents interact with your Xata organizations, projects, and Postgres database branches.
Zero-dependency, token-efficient database MCP server for Postgres, MySQL, SQL Server, MariaDB, SQLite.
MCP server for interacting with Neon Management API and databases
Postgres MCP Pro provides configurable read/write access and performance analysis for you and your AI agents.
A MCP (model context protocol) server that gives the LLM access to and knowledge about relational databases like SQLite, Postgresql, MySQL & MariaDB, Oracle, and MS-SQL.
Comments