Skip to main content
Glama
Pawangunjkar

DB MCP Server

by Pawangunjkar

Related Servers

Alternatives to DB MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language querying of SQL databases using AI, supporting multiple database types and automatic schema discovery.
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI to query and manage PostgreSQL and MongoDB databases through natural language. Supports automatic schema discovery, safe data operations, and network-wide database access with zero-configuration deployment.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language management of your cloud database backend, including running SQL, applying migrations, managing tables, storage, edge functions, and branches, plus searching documentation. Connects via one-click magic-link without keys or tokens.
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables interaction with 20+ databases (PostgreSQL, MongoDB, Neo4j, Elasticsearch, Redis, and more) through a single unified interface, allowing cross-database queries and operations via natural language.
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables executing SQL queries, schema introspection, and data management for PostgreSQL and MySQL databases via natural language, supporting local, SSH, and AWS RDS connections.
      8
      50 npm
      MIT

    TDQS

    C2.9/5.0

    Scored across 23 tools

    Disambiguation5/5

    Every tool is namespaced by engine (db_, mongo_, redis_, es_) and action, making read, write, and administrative operations easy to separate. Even db_execute vs db_insert/update/delete is clear because execute is for arbitrary SQL statements while the specialized tools target row-level operations.

    Naming Consistency4/5

    Tool names follow a mostly consistent <engine>_<operation> pattern, with clear prefixes like db_, mongo_, redis_, and es_. Minor inconsistency exists between verb-only names like db_query, db_execute, and mongo_find versus verb-noun names like db_list_tables and mongo_list_databases.

    Tool Count4/5

    23 tools is slightly above the typical sweet spot, but the server covers four different database engines, so the breadth is justified. Each tool represents a distinct operation and none feel redundant or purely decorative.

    Completeness4/5

    SQL, MongoDB, and Redis have solid CRUD and inspection coverage, and Elasticsearch covers search, indexing, and deletion. Minor gaps exist, such as no ES update/get-by-id, no explicit transaction control, and no SQL database listing, but agents can often work around these with db_execute or search queries.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues