Skip to main content
Glama
entropy-data

Data Product MCP

by entropy-data
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Data Product MCP

No user-submitted related servers found.

    Related Servers

    • MetaGraph-MCP

      midsane
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables enterprise AI agents to query governed data lineage, PII-aware schema documentation, and semantic metadata from SQL logs via MCP, with role-based access and vector search.
      MIT
    • dst by get-dst

      dstofficial

      get-dst
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query governed data warehouses through plain language, returning grounded answers with SQL, confidence grades, and signed receipts while enforcing access, testing, and audit controls.
      11
      Apache 2.0

    • Alma Atlas

      velum-labs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query live schema, lineage, and query-context across data warehouses, dbt projects, orchestration systems, and BI tools via MCP tools.
      Apache 2.0

    • Databricks MCP Server

      proxziima
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to explore Unity Catalog metadata, execute SQL queries, and analyze data lineage including notebooks and jobs, empowering autonomous data discovery and query generation in Databricks.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: search for data products, get full details, request access to an output port, and execute a query. No two tools overlap in function, making selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent pattern of 'dataproduct_' followed by a verb (search, get, request_access, query). The naming convention is uniform and predictable.

    Tool Count5/5

    Four tools cover the essential workflows for this domain: discovery, inspection, access request, and query. This is well-scoped and within the recommended range.

    Completeness4/5

    The core lifecycle is covered, but there is a minor gap: there's no way to list all data products without a search term, which limits catalog browsing. Also, no mechanism for canceling or revoking access requests is provided.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources