mcp-openmetadata
Related Servers
Alternatives to mcp-openmetadata
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables querying Tableau lineage through the Metadata API via MCP, supporting impact analysis, where-used lookups, and content search. Provides read-only tools for answering natural-language questions about workbooks, datasources, fields, and dependencies.7212 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search, explore data lineage, understand business context, and generate SQL queries across an organization's data ecosystem.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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
- FlicenseNot gradedqualityCmaintenanceEnables composable search and filtering over an enterprise data catalog, with tools for lineage, sample data, profiling, history, quality rules, and AI-driven classification.-
- AlicenseNot gradedqualityDmaintenanceEnables extraction and querying of database schema metadata from PostgreSQL, Snowflake, SQL Server, BigQuery, and Oracle databases, saving results locally for analysis.MIT
- AlicenseNot gradedqualityAmaintenanceEnables natural language search and discovery of open-access scientific datasets through the EOSC Data Commons OpenSearch service. Provides tools to search datasets and retrieve file metadata using LLM-assisted queries.15MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: search across entities, retrieve a table, fetch sample data, fetch owners, fetch columns, and list tables. While get_table_by_fqn may return columns as part of the entity, the specific getters are explicitly focused, so an agent can select based on need without confusion.
All tool names follow a consistent verb_noun pattern (get_* and search_*), use lowercase with underscores, and are uniformly structured. There are no mixed conventions or vague verbs.
With 6 tools, the server is well-scoped for a metadata browsing purpose. Each tool provides a distinct capability without redundancy or excessive granularity, fitting comfortably within the ideal range.
The server covers core table read operations (get, list, columns, owners, sample data) and a general entity search. However, it lacks direct retrieval for other metadata entities like databases, schemas, and tags, and has no create/update/delete operations, which are common in metadata management. This leaves notable gaps for a full OpenMetadata surface.