dbt-labs/dbt-mcp

This MCP (Model Context Protocol) server provides various tools to interact with dbt. You can use this MCP server to provide AI agents with context of your project in dbt Core, dbt Fusion, and dbt Platform.
Read our documentation here to learn more. This blog post provides more details for what is possible with the dbt MCP server.
Experimental MCP Bundle
We publish an experimental Model Context Protocol Bundle (dbt-mcp.mcpb) with each release so that MCPB-aware clients can import this server without additional setup. Download the bundle from the latest release assets and follow Anthropic's mcpb CLI docs to install or inspect it.
Feedback
If you have comments or questions, create a GitHub Issue or join us in the community Slack in the #tools-dbt-mcp channel.
Architecture
The dbt MCP server architecture allows for your agent to connect to a variety of tools.
Tools
SQL
Tools for executing and generating SQL on dbt Platform infrastructure.
- execute_sql: Executes SQL on dbt Platform infrastructure with Semantic Layer support.
- text_to_sql: Generates SQL from natural language using project context.
Semantic Layer
To learn more about the dbt Semantic Layer, click here.
- get_dimension_values: Gets distinct values for a dimension; option to scope to specific metrics.
- get_dimensions: Gets dimensions for specified metrics.
- get_entities: Gets entities for specified metrics.
- get_metrics_compiled_sql: Returns compiled SQL for metrics without executing the query.
- list_metrics: Retrieves all defined metrics.
- list_saved_queries: Retrieves all saved queries.
- query_metrics: Executes metric queries with filtering and grouping options.
Discovery
To learn more about the dbt Discovery API, click here.
- get_all_macros: Retrieves macros; option to filter by package or return package names only.
- get_all_models: Retrieves name and description of all models.
- get_all_sources: Gets all sources with freshness status; option to filter by source name.
- get_exposure_details: *(deprecated — use get_node_details instead)*
- get_exposures: Gets all exposures (downstream dashboards, apps, or analyses).
- get_lineage: Gets a bounded lineage graph with type, depth, and direction filtering.
- get_macro_details: *(deprecated — use get_node_details instead)*
- get_mart_models: Retrieves all mart models.
- get_model_children: *(deprecated — use get_lineage instead)*
- get_model_details: *(deprecated — use get_node_details instead)*
- get_model_health: Gets health signals: run status, test results, and upstream source freshness.
- get_model_parents: *(deprecated — use get_lineage instead)*
- get_model_performance: Gets execution history for a model; option to include test results.
- get_node_details: Gets full details for any dbt resource type (model, source, exposure, test, seed, snapshot, macro, semantic_model).
- get_related_models: Finds similar models using semantic search.
- get_seed_details: *(deprecated — use get_node_details instead)*
- get_semantic_model_details: *(deprecated — use get_node_details instead)*
- get_snapshot_details: *(deprecated — use get_node_details instead)*
- get_source_details: *(deprecated — use get_node_details instead)*
- get_test_details: *(deprecated — use get_node_details instead)*
- search: [Alpha] Searches for resources across the dbt project (not generally available).
dbt CLI
Allowing your client to utilize dbt commands through the MCP tooling could modify your data models, sources, and warehouse objects. Proceed only if you trust the client and understand the potential impact.