dbt-mcp and mcp-bigquery-server
These are complementary tools: dbt-labs/dbt-mcp orchestrates data transformations and lineage management, while ergut/mcp-bigquery-server provides the underlying LLM-safe query interface to the BigQuery warehouse where dbt models are typically materialized, allowing them to work together in a data pipeline workflow.
About dbt-mcp
dbt-labs/dbt-mcp
A MCP (Model Context Protocol) server for interacting with dbt.
Exposes dbt project metadata and operations through 40+ tools across Discovery API, Semantic Layer, SQL execution, and dbt CLI capabilities—enabling AI agents to query lineage, model details, metrics, and trigger jobs. Connects to dbt Core, Fusion, and Platform environments, supporting both local manifest inspection and cloud-based operations with optional column-level lineage analysis via the Fusion engine.
About mcp-bigquery-server
ergut/mcp-bigquery-server
A Model Context Protocol (MCP) server that provides secure, read-only access to BigQuery datasets. Enables Large Language Models (LLMs) to safely query and analyze data through a standardized interface.
Implements MCP via Node.js with Google Cloud authentication (supporting both CLI and service account keys), exposing BigQuery tables and materialized views through natural language queries with built-in safety constraints (1GB processing limit, read-only access). Integrates exclusively with Claude Desktop via stdio transport, requiring configuration through the application's config file for direct LLM-to-database communication without manual SQL writing.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work