Skip to main content
Glama
kewinall

Data Platform MCP Server

by kewinall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Data Platform MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • dagsmith

      tmcwilliam707
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing read-only Snowflake metadata tools (schemas, tables, queries, lineage) for agentic data pipeline generation, enabling natural-language-to-pipeline workflows with dbt, Airflow, and Great Expectations.
      1
      MIT

    • 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

    • DataLakeHouseMCP

      Zabi82
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered MCP clients to interact with data lakehouse components including Kafka, Flink, and Trino/Iceberg for managing topics, jobs, catalogs, and executing queries.
      2
      -
    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.3/5.0

    Scored across 21 tools

    Disambiguation4/5

    Tools generally target distinct resources or aspects: data source/schema/table discovery, ETL pipeline metadata, lineage, SQL analysis, and observability. The closest overlap is among get_etl_table_lineage, get_table_lineage, and analyze_sql_lineage, but their producer/catalog/SQL scopes are described enough to avoid frequent misselection.

    Naming Consistency4/5

    Most tools follow a consistent snake_case verb_noun pattern (list_*, get_*, search_*, describe_*). Minor deviations are health and whoami, which are bare commands, and table_statistics, which lacks a get_ prefix.

    Tool Count4/5

    21 tools is slightly above the ideal 3-15 range, but the server spans several coherent subdomains: metadata discovery, ETL, lineage, SQL analysis, and operations. Each tool maps to a distinct operation, so the count does not feel padded.

    Completeness4/5

    For a governed, read-only metadata server the surface covers listing/discovery, table details, ETL lifecycle metadata, lineage, DAG status, logs, and runbooks. Minor gaps such as no dedicated getters for individual data sources/schemas and no downstream lineage are workaround-able but would improve full coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources