Skip to main content
Glama
qraza

dbt-mcp

by qraza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to dbt-mcp

No user-submitted related servers found.

    Related Servers

    • @us-all/dbt-mcp

      us-all
      A
      license
      B
      quality
      C
      maintenance
      A 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.
      27
      28 npm
      MIT

    • Data Product Hub

      armalite
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server that provides comprehensive dbt project quality assessment for any GitHub repository, enabling AI agents to analyze dbt models, check metadata coverage, and map data lineage.
      9
      MIT

    • dbt-doctor

      Astoriel
      A
      license
      Not graded
      quality
      D
      maintenance
      AI-driven MCP server that audits, profiles, detects schema drift, and auto-generates documentation for dbt projects, enabling natural language interaction with your dbt project's health.
      124
      MIT

    • dbt-mcp

      bratko1234
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides tools to interact with dbt, including dbt Core, Cloud CLI, Semantic Layer, and Discovery API.
      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
    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

    A4.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: run_summary provides a high-level overview, list_failing_tests enumerates failures in detail, sample_failing_rows retrieves offending rows, and health checks configuration. Even though run_summary and list_failing_tests both relate to failing tests, they operate at different levels of detail, leaving no ambiguity.

    Naming Consistency4/5

    Most tool names follow a consistent verb_noun pattern (run_summary, list_failing_tests, sample_failing_rows). However, 'health' breaks the pattern as a single noun rather than a verb_noun construct, a minor but noticeable deviation.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of analyzing dbt test failures. Each tool earns its place, and the count is appropriate for a focused domain without feeling thin or bloated.

    Completeness5/5

    The tool set covers the full workflow: verifying setup (health), getting a summary (run_summary), drilling into failures (list_failing_tests), and examining specific rows (sample_failing_rows). No obvious missing operations within the stated scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources