Skip to main content
Glama
jaynasriwala

Universal Database MCP

by jaynasriwala

Related Servers

Alternatives to Universal Database MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that lets LLMs explore SQLite databases in plain English, with enforced write protection and sensitive column redaction.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that lets AI agents safely query SQLite, PostgreSQL, and MySQL/MariaDB. Enforces read-only transactions with column masking, row caps, query timeouts, EXPLAIN-based cost rejection, and rate limiting.
      7
      44 npm
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for querying PostgreSQL, MySQL, and SQLite from AI agents — multi-database, safe by default.
      4
      16 npm
      1
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides safe, read-only SQL access for AI agents to query databases (PostgreSQL, MySQL, SQLite) with schema awareness and guardrails.
      15 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that exposes PostgreSQL/MySQL/SQLite/MongoDB databases to AI agents, converting natural language questions into SQL queries with configurable LLM providers and safe read-only operations.
      -
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that provides safe, read-only access to a PostgreSQL warehouse, enabling schema introspection, guarded SQL queries, and truncated result reporting for LLMs.
      3
      MIT

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation4/5

    get_database_schema and explain_sql_query are clearly distinct from each other. However, export_results_format and execute_safe_query both run read-only queries, and the difference (reshaping/output format vs. raw results) is only clear from the description, creating mild overlap.

    Naming Consistency4/5

    All names use snake_case with a verb-first pattern (export_, get_, execute_, explain_), which is predictable and readable. export_results_format is slightly awkward (verb_noun_noun) but still follows the convention.

    Tool Count4/5

    Four tools is lean but well-scoped for a read-only, safety-focused query server; each tool covers a distinct capability (schema, query, plan, export). It sits just above the thin end of the range but earns its place.

    Completeness4/5

    The read-only lifecycle is well covered: discover schema, inspect plans, run queries, and export results. Gaps are minor, such as no way to list available databases/connections, but the stated read-only purpose is served without dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues