mcp-turso-cloud
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TURSO_API_TOKEN | Yes | Your Turso Platform API token | |
| TOKEN_EXPIRATION | No | Expiration time for generated database tokens | 7d |
| TOKEN_PERMISSION | No | Permission level for generated tokens | full-access |
| TURSO_ORGANIZATION | Yes | Your Turso organization name | |
| TURSO_DEFAULT_DATABASE | No | Default database to use when none is specified |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_databasesA | List all databases in your Turso organization |
| create_databaseC | ✓ SAFE: Create a new database in your Turso organization. Database name must be unique. |
| delete_databaseB | ⚠️ DESTRUCTIVE: Permanently deletes a database and ALL its data. Cannot be undone. Always confirm with user before proceeding and verify correct database name. |
| generate_database_tokenC | Generate a new token for a specific database |
| list_tablesC | Lists all tables in a database |
| execute_read_only_queryB | ✓ SAFE: Execute read-only SQL queries (SELECT, PRAGMA, EXPLAIN). Automatically rejects write operations. |
| execute_queryC | ⚠️ DESTRUCTIVE: Execute SQL that can modify/delete data (INSERT, UPDATE, DELETE, DROP, ALTER). Always confirm with user before destructive operations. |
| describe_tableC | Gets schema information for a table |
| vector_searchD | Performs vector similarity search |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: database CRUD, querying (read-only vs. destructive), schema inspection, token generation, listing resources, and vector search. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_database, execute_query, list_tables), making the set predictable and easy to navigate.
9 tools is well-scoped for a cloud database service covering management, querying, schema, tokens, and vector search. No unnecessary tools and no deficit.
Core operations are covered (CRUD for databases, query execution, schema inspection, token generation). Minor gaps like listing or revoking tokens exist, but the surface is mostly complete for typical workflows.