Skip to main content
Glama
frothkoetter

data-marketplace-mcp-server

by frothkoetter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to data-marketplace-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCP Data Catalog Server

      akashmanjini
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables composable search and filtering over an enterprise data catalog, with tools for lineage, sample data, profiling, history, quality rules, and AI-driven classification.
      -

    • Data Product MCP

      entropy-data
      A
      license
      A
      quality
      F
      maintenance
      Enables AI agents to discover, request access to, and query data products in Data Mesh Manager, enforcing governance policies while retrieving business data from platforms like Snowflake and Databricks.
      4
      46
      MIT

    • iceberg-mcp-server-hive

      frothkoetter
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only SQL access to Apache Iceberg tables via HiveServer2, enabling querying, schema discovery, and database listing on Cloudera Data Platform.
      3
      Apache 2.0

    • GTM Data MCP

      kenlim-mops
      F
      license
      B
      quality
      C
      maintenance
      Provides AI clients with a governed, searchable catalog of go-to-market context, including ownership, measurement, lineage, runbooks, and bulk-change templates. Optionally integrates with the UTM Builder for governed UTM reference data, preview, and issuance.
      15
      -

    • 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
    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

    B3/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: searching, viewing, requesting access, publishing, and sync operations cover separate concerns. However, list_access_requests and list_product_subscribers both deal with subscribers/access and could cause some confusion about which to use for a given scenario.

    Naming Consistency4/5

    The naming follows a strong verb_noun pattern (search_data_products, get_data_product, preview_data_product, publish_data_product, certify_data_product). Minor deviations exist: ensure_data_marketplace_typedef and get_product_lineage break the strict pattern but are still readable and descriptive.

    Tool Count4/5

    At 16 tools, this sits slightly above the ideal sweet spot but is reasonable for a marketplace with search, product lifecycle, access management, and Atlas sync capabilities. Most tools earn their place, though the two ‘WRITE OPERATION’ Atlas sync tools are somewhat operational rather than user-facing.

    Completeness4/5

    The surface covers search, view, preview, lineage, glossary, access lifecycle (request/list/approve/reject), publishing, certification, and feedback. Minor gaps include no explicit update/delete for data products (only publish/create) and subscription management beyond listing, but the core marketplace workflow is well covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources