Skip to main content
Glama
ai-ready-warehouse

ai-ready-warehouse

by KNMDeep

Related Servers

Alternatives to ai-ready-warehouse

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets an AI assistant explore and query Postgres, DuckDB, or Snowflake with read-only SQL, table and schema discovery, sampling, and explainable guardrails.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Query SQL databases (SQLite, PostgreSQL, BigQuery, Databricks) in natural language through a business semantic layer — glossary, metrics, and a data dictionary grounded against your real schema. Read-only by default, with an embedded SQLite + sqlite-vec metadata store and no external infra required.
      25
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants such as Claude, ChatGPT and Cursor to safely explore database schemas and answer business questions by running read-only SQL queries in plain English.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives an LLM read-only, schema-aware SQL database access so users can ask business questions in plain English and receive the exact result set, with malformed queries returned as errors for automatic retry and correction.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover and query PostgreSQL, MySQL, SQL Server, and Oracle databases through 18 read-only tools served over streamable HTTP or stdio. Every call runs under the caller's row-level rules and column masks against a human-approved data catalog and leaves one audit event.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents governed context about a data warehouse — table meaning, ownership, lineage, freshness, and PII flags — plus read-only, row-limited, PII-protected querying across DuckDB, Snowflake, and Databricks. Guardrails enforced at parsing, connection, and result layers keep agents from writing, running away, or leaking personal data.
      86 PyPI
      MIT

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools form a clean discovery-then-execute pipeline: list_tables finds tables, describe_table inspects a single table's columns, and query executes SQL. Each has a distinct scope with no functional overlap, so an agent can select unambiguously.

    Naming Consistency4/5

    list_tables and describe_table follow a consistent verb_noun snake_case pattern, and query fits the short imperative style of the set. The only minor deviation is that query is a bare verb rather than verb_noun, but it is still predictable and readable.

    Tool Count4/5

    Three tools is on the lean side but well matched to a read-only warehouse exploration surface — discovery, inspection, and execution each earn their place. A fourth tool (e.g. sample rows or schema listing) could add value, but nothing here is redundant.

    Completeness4/5

    The core read-only lifecycle — find tables, understand their columns, and run SELECT/WITH queries — is fully covered, and query acts as a universal escape hatch for anything not directly supported. Minor gaps like previewing sample rows or listing distinct schemas are workable via SQL, though write operations are intentionally absent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues