dbt-mcp and mcp-server-bigquery
These are complements: dbt is a transformation tool that orchestrates SQL workflows, while BigQuery is a data warehouse backend, so dbt-mcp would typically use the BigQuery MCP server to interact with BigQuery as dbt's target database.
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-server-bigquery
LucasHild/mcp-server-bigquery
A Model Context Protocol server that provides access to BigQuery
Exposes three tools for LLM interaction: `execute-query` for BigQuery SQL execution, `list-tables` for schema discovery, and `describe-table` for inspecting column definitions. Communicates via stdio transport and integrates directly with Claude Desktop and Cursor through MCP configuration, supporting GCP authentication via service account keys or default credentials. Supports dataset filtering and configurable query timeouts to control execution scope and resource consumption.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work