mcp-turso

Created By
nbbaiera year ago
MCP server for interacting with Turso-hosted LibSQL databases
Overview

What is mcp-turso?

Mcp-turso is a Model Context Protocol (MCP) server designed for interacting with Turso-hosted LibSQL databases, enabling users to perform various database operations.

How to use mcp-turso?

To use mcp-turso, configure it with your Turso database URL and authentication token in the claude_desktop_config.json file, and run the server using NPX.

Key features of mcp-turso?

  • Retrieve a list of tables in a database.
  • View the database schema.
  • Get the schema of a specific table.
  • Execute SELECT queries to read data from the database.

Use cases of mcp-turso?

  1. Managing and querying data in Turso-hosted databases.
  2. Integrating database functionalities into applications using the MCP protocol.
  3. Debugging and logging database interactions for development purposes.

FAQ from mcp-turso?

  • What is required to use mcp-turso?

You need a Turso database and the corresponding URL and authentication token.

  • Can I customize the logging path?

Yes, you can specify a custom logging path in the server's configuration.

  • Is there a license for mcp-turso?

Yes, it is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nbbaier
Star
5
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

6 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago