mcp-server
Related Servers
Alternatives to mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables MCP hosts like ChatGPT and Claude to query data platform metadata, explore schemas and tables, inspect SQL explain plans, and monitor DAG and ETL status through standardized tools.21MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to browse BigQuery datasets and table metadata, run capped read-only SQL with cost estimates and dry runs, trace upstream/downstream table lineage, and fetch Dataplex data-quality scan results over a streamable-http endpoint on Cloud Run.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover schemas, keys, and lineage across bronze, silver, and gold tables, and to run guarded read-only SQL queries against the lakehouse.1MIT
- AlicenseAqualityBmaintenanceProvides read-only tools that let Claude and other MCP clients investigate data quality issues such as metric drops, duplicates, join fan-out, freshness problems, and dbt test failures by profiling local CSV, Parquet, NDJSON, DuckDB, Postgres, and dbt artifacts.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables language models to safely explore lakehouse tables and governed metrics, run guarded read-only SQL, and inspect pipeline health and data-contract violations through MCP tools.MIT
- AlicenseBqualityCmaintenanceA read-only MCP server that exposes dbt project artifacts and data quality result tables (BigQuery/Postgres) to LLM clients, enabling deep introspection, run-history analysis, source freshness, test coverage, and lineage walks.2742 npmMIT
TDQS
Scored across 6 tools
Each tool targets a clearly different need: slice-by-dimension (breakdown), time series (daily_totals), metadata (list/explain), and pipeline trust (freshness/quality_report). The only mild overlap is between metrics_freshness and metrics_quality_report, since freshness surfaces quality_status and points to the report, but the split between run identity/date coverage and check-level detail is explained well.
All six tools share the metrics_ namespace prefix and snake_case suffixes, giving a strongly predictable pattern. The suffixes mix verbs (explain, list) with nouns (breakdown, daily_totals, quality_report, freshness), which is a minor deviation but still very readable.
Six tools is well-scoped for a metrics query server: discovery (list, explain), retrieval (daily_totals, breakdown), and trust (freshness, quality_report) each get dedicated tools with no filler. Nothing looks redundant or missing at the count level.
The surface covers the full query lifecycle—discover metrics, understand definitions, pull totals and breakdowns across grains, and verify data currency and quality—with no obvious dead ends. The main gap is there is no way to enumerate valid `by` dimensions or category/distribution-center values, so an agent must discover them by trial or from breakdown results.