Skip to main content
Glama
sam2332

SQLite MCP Server

by sam2332

Related Servers

Alternatives to SQLite MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server implementation that enables AI assistants to execute SQL queries and interact with SQLite databases through a structured interface.
      7
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol (MCP) server for SQLite database operations. This server enables AI assistants to interact with SQLite databases through a standardized interface.
      262 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Implements a Model Context Protocol server that enables natural language interactions with SQLite databases, providing tools to list tables, retrieve schemas, count rows, and execute read-only SQL queries.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides SQLite database operations. Allows AI assistants to query, modify and manage SQLite databases through the Model Context Protocol.
      -
    • A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that enables SQL operations (SELECT, INSERT, UPDATE, DELETE) and table management through a standardized interface with SQLite databases.
      7
      57 npm
      1
      ISC
    • 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.
      958 npm
      382
      MIT

    TDQS

    B3.2/5.0

    Scored across 6 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes that could cause confusion. For example, 'describe_table' and 'get_table_info' both seem to provide table schema information, and 'execute_query' and 'query_data' both handle SQL queries with unclear boundaries (e.g., whether SELECT queries should use 'execute_query' or 'query_data'). This overlap makes it difficult for an agent to reliably choose the right tool.

    Naming Consistency4/5

    The tool names follow a consistent verb_noun pattern throughout (e.g., connect_database, describe_table, execute_query), which is predictable and readable. There are no deviations in naming conventions, though the verbs could be more precise to reduce ambiguity.

    Tool Count5/5

    With 6 tools, the server is well-scoped for interacting with SQLite databases. This count covers essential operations like connecting, listing tables, describing schemas, and executing queries, without being overly complex or too sparse. Each tool appears to earn its place in the set.

    Completeness4/5

    The tool set covers core database operations such as connection, table listing, schema inspection, and query execution, which are sufficient for most SQLite workflows. However, there is a minor gap in not having explicit tools for database management tasks like creating or dropping tables, though these could be handled via 'execute_query'. This does not significantly hinder agent functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues