Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to openmetadata-mcp-server

No user-submitted related servers found.

    Related Servers

    • bonnard by bonnard-data

      bonnardofficial

      bonnard-data
      A
      license
      Not graded
      quality
      F
      maintenance
      Open-source agentic schema layer. Define metrics once in YAML, query governed data from any warehouse (Snowflake, BigQuery, Databricks, PostgreSQL, DuckDB) via MCP.
      28
      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

    • Data Workers

      DataWorkersProject
      F
      license
      Not graded
      quality
      C
      maintenance
      Open-source autonomous agent swarm of 15 MCP-native AI agents for data engineering — catalog, quality, incidents, schema evolution, governance, migration, observability, ML. 212+ tools, Apache 2.0. Works with Claude Code, Cursor, ChatGPT, and any MCP client.
      12
      -

    • Datris MCP Server

      datris
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server with 32 tools for ETL ingestion, AI-generated data quality rules, AI transformations, vector search, and natural-language SQL. Works across Postgres, MongoDB, Kafka, S3/MinIO, HashiCorp Vault, and five vector stores (Qdrant, Weaviate, Milvus, Chroma, pgvector).
      12
      AGPL 3.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
    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

    C2.6/5.0

    Scored across 173 tools

    Disambiguation4/5

    The list/get/create/update/delete pattern per entity type makes most tools easy to tell apart, and UUID vs FQN variants are explicitly labeled in each description. A few aggregated and validation tools overlap conceptually (validate-data-contract vs run-data-contract-validation, get-table-summary vs get-table + get-lineage), but those descriptions are differentiated enough to avoid major mis-selection.

    Naming Consistency4/5

    Overwhelmingly consistent: almost every tool uses lowercase snake_case with a verb-noun pattern like list-tables, get-table-by-name, and update-database. The small set of aggregate/utility tools (semantic-search, lineage-impact, quality-rollup, search-tools) deviates slightly from that pattern but still reads clearly.

    Tool Count1/5

    173 tools is far beyond the extreme-mismatch threshold and will overwhelm agents, even with search-tools as a navigation aid. The per-entity CRUD expansion could be parameterized into a much smaller set without losing capability.

    Completeness4/5

    The set gives deep lifecycle coverage for most core data assets—tables, databases, schemas, dashboards, pipelines, topics, glossaries, teams, and domains—plus lineage, sample data, quality rollups, and data-contract validation. The main gaps are read-only admin surfaces (users, roles, policies, metrics, API collections, search indexes) and missing create/update for some service types, which are workable but noticeable.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources