Dbt MCP Server

If you want an AI assistant working directly with Dbt, the dbt mcp server is the bridge. Official MCP server for dbt (data build tool) providing integration with dbt Core/Cloud CLI, project metadata discovery, model information, and semantic layer querying capabilities.

What Dbt does

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.

Tools it exposes

Once connected, the assistant can call these 11 tools directly:

• cancel_job_run — Cancels a running job
• get_job_details — Gets job configuration including triggers, schedule, and dbt commands
• get_job_run_details — Gets run details including status, timing, steps, and artifacts
• get_job_run_error — Gets error and/or warning details for a job run; option to include or show warnings only
• list_job_run_artifacts — Lists available artifacts from a job run
• list_jobs — Lists jobs in a dbt Platform account; option to filter by project or environment
• list_jobs_runs — Lists job runs; option to filter by job, status, or order by field
• list_projects — Lists all projects in the dbt Platform account
• retry_job_run — Retries a failed job run
• trigger_job_run — Triggers a job run; option to override git branch, schema, or other settings
• Discovery — To learn more about the dbt Discovery API, click here. - get_all_macros: Retrieves macros; option

Installing the dbt mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Dbt sits in that group, and the shape of its toolset — cancel_job_run, get_job_details, get_job_run_details among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• With 11 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Dbt.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the dbt mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.