Skip to main content
Glama
nbbaier

MCP-Turso

by nbbaier

Related Servers

Alternatives to MCP-Turso

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      This server enables Claude to directly interact with SQLite, SQL Server, PostgreSQL, and MySQL databases through the Model Context Protocol, allowing for query execution, table management, and data export capabilities.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Exposes a Turso (libSQL) database to Claude via HTTP/SSE, enabling table listing, schema inspection, and read/write SQL queries.
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that enables LLMs like Claude to interact with SQLite and SQL Server databases, allowing for schema inspection and SQL query execution.
      569 npm
      382
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that enables Claude and other LLMs to perform database operations and invoke Edge Functions within Supabase through natural language.
      1,809 npm
      4
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      🗂️ 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.
      9
      74 npm
      18
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows Large Language Models like Claude to execute SQL queries, explore database schemas, and maintain persistent connections to SQL Server databases.
      -

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive