Data Product MCP
Related Servers
Alternatives to Data Product MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to search, explore data lineage, understand business context, and generate SQL queries across an organization's data ecosystem.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables 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.159 PyPI18Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents to answer analytics questions with provable correctness by resolving metrics through the semantic layer, tracing lineage, traversing knowledge graphs, checking freshness, and searching glossary definitions, while enforcing access controls and logging every call.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to query databases correctly by serving governed context over MCP, including canonical metric definitions, relationships, business meaning, and guardrails, so answers come back with resolved definitions, fired filters, freshness, and a trust score instead of guesses.3-
- AlicenseNot gradedqualityBmaintenanceGives AI agents governed context about a data warehouse — table meaning, ownership, lineage, freshness, and PII flags — plus read-only, row-limited, PII-protected querying across DuckDB, Snowflake, and Databricks. Guardrails enforced at parsing, connection, and result layers keep agents from writing, running away, or leaking personal data.86 PyPIMIT
TDQS
Scored across 4 tools
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.
All tools follow a consistent pattern of 'dataproduct_' followed by a verb (search, get, request_access, query). The naming convention is uniform and predictable.
Four tools cover the essential workflows for this domain: discovery, inspection, access request, and query. This is well-scoped and within the recommended range.
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.