Skip to main content
Glama
universal-db-mcp

universal-db-mcp

by joyous-coder

Related Servers

Alternatives to universal-db-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query and analyze databases using natural language through MCP and HTTP API, supporting 17+ databases and integration with 50+ platforms.
      127 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query and analyze databases using natural language through MCP and HTTP API. Supports 17+ databases and integrates with 55+ platforms.
      127 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to connect to and interact with PostgreSQL, MySQL, SQLite, and MongoDB databases through natural language, supporting schema exploration, query execution, data export, and more.
      13
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM agents to connect to and retrieve data from PostgreSQL, MySQL, SQLite, BigQuery, Oracle, MS SQL, and Redshift via a unified MCP API, with schema normalization, query optimization, and secure connections.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM agents to connect to and retrieve data from multiple database types through a unified MCP API, with schema normalization and query transformation. Supports PostgreSQL, MySQL, SQLite, BigQuery, Oracle, MS SQL, and Redshift.
      -

    TDQS

    B3/5.0

    Scored across 42 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and the descriptions effectively separate the many execute_* variants and schema/profile tools. A few pairs (e.g., explain_query vs. explain_query_with_advice, get_schema vs. get_table_info) could be confused at a glance, but the descriptions provide enough boundary.

    Naming Consistency5/5

    The tool set consistently follows a snake_case verb_noun pattern throughout (execute_query, get_schema, list_templates, create_profile). Minor exceptions like audit_log are negligible; the naming convention is highly predictable.

    Tool Count2/5

    42 tools is well beyond the 25+ threshold for a coherent tool surface. While the universal DB scope explains some breadth, many tools (e.g., execute_query/script/file/batch/templace and multiple export/import variants) could be consolidated without losing functionality.

    Completeness4/5

    The tool surface covers core database operations, schema inspection, profile lifecycle, templates, PII config, import/export, backup, audit, and query planning. Minor gaps include no explicit transaction-control tool and no dedicated schema-modification operations beyond generic execute_query.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues