Skip to main content
Glama
mcp-database-server

mcp-database-server

by uidoyen

Related Servers

Alternatives to mcp-database-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to safely explore and query a SQLite database through natural language, including listing tables, inspecting schemas, and running read-only SELECT queries.
      711 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude and other MCP clients to inspect a local SQLite database's tables, columns, and schema, and run safe read-only SQL queries with capped JSON results.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude and other MCP clients to map a SQLite database's schema and run read-only SQL queries against it, with writes blocked at the SQLite level through multiple enforcement layers. Results come back as context-friendly Markdown tables with row caps and a query timeout.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets Claude Desktop, Claude Code, and other MCP clients map the structure of a SQLite database and run read-only SQL queries against it, returning compact Markdown results. Multi-layered protections make any write impossible, so a database can be explored without reviewing each query first.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes any SQLite database as read-only MCP tools for AI assistants, enabling listing tables, describing schemas, and running SELECT queries with filtering, ordering, and pagination.
      -

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct step in the workflow: discovery (list_tables), schema inspection (describe_table), and data retrieval (run_query). There is no meaningful overlap, and describe_table's argument explicitly references list_tables' output.

    Naming Consistency5/5

    All three tools use a consistent snake_case verb_noun pattern (list_tables, describe_table, run_query). The naming is predictable and self-explanatory.

    Tool Count4/5

    Three tools is minimal but well-matched to a read-only SQL exploration surface; each earns its place. It sits at the low end, though run_query alone could handle much of the work, making the set feel slightly thin.

    Completeness4/5

    The read-only discovery-plus-query lifecycle is fully covered, and run_query is a general escape hatch for anything else. Write operations are intentionally excluded (documented as read-only), so this is a deliberate scope limit rather than a gap, though no schema-dump or pagination aid exists.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues