MCP-Turso
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TURSO_AUTH_TOKEN | Yes | Your Turso database authentication token (obtain via 'turso db tokens create <database-name>') | |
| TURSO_DATABASE_URL | Yes | The URL of your Turso database (obtain via 'turso db show --url <database-name>') |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesB | List all tables in the database |
| get_db_schemaB | Get the schema for all tables in the database |
| describe_tableC | View schema information for a specific table |
| query_databaseC | Execute a SELECT query to read data from the database |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: describe_table focuses on a single table's schema, get_db_schema covers all tables' schemas, list_tables simply enumerates table names, and query_database handles data retrieval. An agent can easily differentiate these based on their specific scopes.
All tools follow a consistent verb_noun pattern (describe_table, get_db_schema, list_tables, query_database) with clear, descriptive names. The naming is uniform and predictable, making it easy for agents to understand the action and target.
With 4 tools, this server is well-scoped for database interaction, covering essential operations like schema inspection, table listing, and data querying. Each tool earns its place without feeling excessive or insufficient for the domain.
The tools provide solid coverage for read-only database operations, including schema exploration and data querying. However, there are minor gaps for a full database management scope, such as lacking write operations (e.g., insert, update, delete) or administrative functions, which agents might need to work around.