Skip to main content
Glama
HumanSamadian

Data Nexus MCP

Related Servers

Alternatives to Data Nexus MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with heterogeneous databases (MySQL, MongoDB, BigQuery) through MCP tools, allowing natural language queries and database operations.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides universal database operations for AI assistants through MCP, supporting 40+ databases including PostgreSQL, MySQL, MongoDB, Redis, and SQLite with built-in introspection tools for schema exploration.
      19 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to inspect real databases through MCP with tools for listing tables, describing schemas, sampling rows, running queries, and explaining execution plans, all with engine-enforced read-only access to SQLite and MySQL.
      5
      14 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs and agents to interact with relational databases (SQL Server, MySQL, PostgreSQL) through MCP tools. Supports executing queries, inserting records, listing tables, and exposing database schemas with secure credential management.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Gives AI agents direct access to databases across 8 engines with 145+ tools, enabling schema-aware query execution and management through natural language.
      17
      57 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect to and interact with MySQL, Redis, and MongoDB through a stdio MCP server, with unified data source discovery, read-only querying, and explicitly authorized write operations.
      MIT

    TDQS

    B3/5.0

    Scored across 5 tools

    Disambiguation4/5

    Tools are mostly distinct: query_database and execute_sql both run queries but one is parameterized and the other raw; get_schema, list_tables, describe_table each target different metadata. Minor potential for confusion between the two query tools, but descriptions clarify the difference.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores: query_database, get_schema, list_tables, describe_table, execute_sql. No mixed conventions or irregularities.

    Tool Count5/5

    5 tools are well-scoped for a database MCP server. The set covers core operations—querying, schema retrieval, table listing, structure description, raw execution—without being overwhelming or too sparse.

    Completeness4/5

    The tool surface covers essential query and schema exploration operations. The execute_sql tool can handle DDL, but there are no dedicated create/alter/drop tools; transaction commands are also missing. Overall, it's nearly complete for a typical read-heavy interaction pattern.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues