MCP Turso
Related Servers
Alternatives to MCP Turso
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol server that provides Claude access to Turso-hosted LibSQL databases, enabling database table listing, schema retrieval, and SELECT query execution.484 npm6MIT
- AlicenseNot gradedqualityAmaintenanceProvides tools for interacting with PlanetScale databases via the Model Context Protocol, enabling database operations through natural language or API calls.261 npm5Apache 2.0
- AlicenseBqualityCmaintenance🗂️ 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 from LLMs.974 npm18MIT
- AlicenseNot gradedqualityFmaintenanceProvides AI-IDEs with real-time access to PostgreSQL and Supabase database schemas through the Model Context Protocol, enabling smarter code generation in tools like Cursor, Windsurf, and VS Code + Cline.9MIT
- AlicenseNot gradedqualityDmaintenanceEnables managing Neon projects, databases, and running SQL queries through natural language via Model Context Protocol.1,523 npmMIT
- FlicenseNot gradedqualityDmaintenanceQuery, explore, and manage SQLite databases through the Model Context Protocol. Connect any MCP-compatible AI client to your databases.-
TDQS
Scored across 14 tools
Each tool targets a specific database operation, making most purposes clear. The only mild ambiguity is that add_constraint, add_column, and create_index overlap conceptually with generic execute_ddl, but their dedicated descriptions resolve the intent.
All tools use a consistent snake_case verb_noun pattern such as list_tables, insert_data, begin_transaction, and create_index. This creates a predictable and easily navigable API surface.
14 tools is well within the ideal range for a database-focused MCP server. Each tool has a clear role, covering introspection, data manipulation, DDL, and transaction control without unnecessary redundancy.
The surface covers the core database lifecycle: schema inspection, CRUD, counting, constraints, indexes, column additions, generic DDL, and transaction management. The inclusion of execute_ddl fills any long-tail DDL gaps, so agents are unlikely to hit dead ends.