mcp-turso
About
MCP server for interacting with Turso-hosted LibSQL databases
Details
- Author
- nbbaier
- GitHub stars
- 6
- Downloads
- 433
- Categories
- Database, AI
Jump to
- List all tables in a Turso database
- Retrieve full database schema as SQL statements
- Describe a specific table’s column names and types
- Execute SELECT queries and return results
- Custom logging support for debugging
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
mcp-tursoCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Add the server to your MCP client's configuration (e.g., in Claude Desktop or Cursor) by running npx -y mcp-turso and setting the environment variables TURSO_DATABASE_URL and TURSO_AUTH_TOKEN. You need an existing Turso database with its URL and token, which you can obtain via the Turso CLI. Logs are written by default to ~/.npm/_npx/<npx-dir-name>/node_modules/mcp-turso/logs/mcp-turso.log, and a custom path can be specified with the --logs flag (absolute posix path).
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp-turso": {
"turso": {
"command": "npx",
"args": [
"-y",
"mcp-turso"
],
"env": {
"TURSO_DATABASE_URL": "",
"TURSO_AUTH_TOKEN": ""
}
}
}
}
}McpServers
{
"turso": {
"command": "npx",
"args": [
"-y",
"mcp-turso"
],
"env": {
"TURSO_DATABASE_URL": "",
"TURSO_AUTH_TOKEN": ""
}
}
}mcp-turso
A Model Context Protocol (MCP) server that provides access to the Turso-hosted LibSQL databases. Currently, the server provides the following functionality:
- Retrieving a list of tables in a database
- Retrieving a database's schema
- Retrieving the schema of a table
- Performing SELECT queries
Configuration
With Claude Desktop
Add this to your claude_desktop_config.json:
{
"mcpServers": [
"turso": {
"command": "npx",
"args": ["-y", "mcp-turso"],
"env": {
"TURSO_DATABASE_URL": "your_url",
"TURSO_AUTH_TOKEN": "your_token"
}
}
]
}
You will need an existing database to continue. If you don't have one, create one. To get the database URL via the Turso CLI, run:
turso db show --url <database-name>
Then get the database authentication token:
turso db tokens create <database-name>
Add those values to your configuration as shown above.
With Cursor
To configure the Turso MCP server with Cursor, add the following to your Cursor settings:
1. Open Cursor and go to Settings (⚙️) > Settings (JSON)
2. Add the following configuration to your settings JSON:
"mcpServers": {
"turso": {
"command": "npx",
"args": ["-y", "mcp-turso"],
"env": {
"TURSO_DATABASE_URL": "your_url",
"TURSO_AUTH_TOKEN": "your_token"
}
}
}
Replace your_url and your_token with your Turso database URL and authentication token as described in the previous section.
Logging
The server includes a custom logger for debugging outside of Claude Desktop. By default, this logger writes to <parent-dir>/logs/mcp-turso.log, where <parent-dir> is the parent directory of directory containing the mcp-turso script. In other words, if the path to mcp-turso is ~/foo/bin/mcp-turso, the logs will be at ~/foo/logs/mcp-turso.log. If running with NPX as above, the default logs will be:
~/.npm/_npx/<npx-dir-name>/node_modules/mcp-turso/logs/mcp-turso.log
If you would like to specify a custom path, you can include a --logs flag with an absolute posix path in the server's configuration:
{
"mcpServers": [
"turso": {
"command": "npx",
"args": ["-y", "mcp-turso", "--logs", "/Users/<username>/path/to/dir/mcp-logs.log"],
"env": {
"TURSO_DATABASE_URL": "your_url",
"TURSO_AUTH_TOKEN": "your_token"
}
}
]
}
The path to the log file (default or custom) is always logged to stderr when the server is created. For Claude desktop, this will show up in your server logs in ~/Library/Logs/Claude.
_Note_: Right now, I haven't implemented specifying a custom logging file for Windows, but this is coming.
Server Capabilities
The server provides the following tools:
- list_tables
- Get a list of all the tables in the database
- No input
- Returns: an array of table names
- get_db_schema
- Get the schemas of all tables in the database
- No input
- Returns: an array of SQL creation statements
- describe_table
- View schema information for a specific table
- Input:
- table_name (string): Name of table to describe
- Returns: Array of column definitions with names and types
- query_database
- Execute a SELECT query to read data from the database
- Input:
- sql (string): The SELECT SQL query to execute
- Returns: Query results as an object of type { columns: string[]; rows: Record<string, unknown>[]; rowCount: number; }
Todo
- [ ] Add the ability to specify a custom log file on windows
- [ ] Add more query tools
License
MIT License - see the LICENSE file for details.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
