dbt-mcp and dremio-mcp
These are complements: dbt transforms and models data within a warehouse while Dremio virtualizes and catalogs data across distributed sources, so they're typically used together in a modern data stack where dbt handles transformation logic and Dremio handles data discovery and virtualization.
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 dremio-mcp
dremio/dremio-mcp
Dremio MCP server
Implements an MCP (Model Context Protocol) server that connects Claude Desktop with Dremio through stdio and streaming HTTP transports, enabling LLMs to query and analyze Dremio datasets. Supports both local (desktop) and Kubernetes deployments with OAuth authentication, automatic reconnection, and Prometheus metrics. Exposes Dremio's data catalog and query capabilities as tools that Claude can invoke directly.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work