Skip to main content
hc
Submit
mcpSource-backed

dbt MCP Server

Official dbt Labs MCP server that gives AI agents context from dbt Core, dbt Fusion, dbt Platform, project metadata, SQL tools, lineage, Admin API, and dbt documentation search.

by dbt Labs · submitted by JSONbored·added 2026-06-05·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/dbt-mcp-server
Source URLs
https://github.com/dbt-labs/dbt-mcp
Safety notes
SQL and admin tools can inspect or affect real analytics environments depending on credentials., Start with read-oriented docs and metadata tools before enabling execution paths.
Privacy notes
dbt metadata, SQL, lineage, model names, run artifacts, and platform account details can expose private analytics structure.
Author
dbt Labs
Submitted by
JSONbored
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

15 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

2 to clear

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

2 prerequisites to line up before setup. Have accounts and credentials ready first.

0/2 ready
Account & credentials215 minutes

Safety & privacy surface

Safety & privacy surface

2 safety and 1 privacy notes across 3 risk areas. Review closely: credentials & tokens.

3 areas
  • SafetyCredentials & tokensSQL and admin tools can inspect or affect real analytics environments depending on credentials.
  • SafetyLocal filesStart with read-oriented docs and metadata tools before enabling execution paths.
  • PrivacyExecution & processesdbt metadata, SQL, lineage, model names, run artifacts, and platform account details can expose private analytics structure.

Safety notes

  • SQL and admin tools can inspect or affect real analytics environments depending on credentials.
  • Start with read-oriented docs and metadata tools before enabling execution paths.

Privacy notes

  • dbt metadata, SQL, lineage, model names, run artifacts, and platform account details can expose private analytics structure.

Prerequisites

  • dbt project, dbt Core/Fusion environment, or dbt Platform account.
  • MCP client and credentials appropriate to the dbt features enabled.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
intermediate
Full copyable content
{
  "mcpServers": {
    "dbt": {
      "command": "uvx",
      "args": ["dbt-mcp"]
    }
  }
}

About this resource

Content

dbt MCP Server is dbt Labs' official Model Context Protocol server for exposing dbt context to AI agents. The repository describes tools for dbt Core, dbt Fusion, dbt Platform, SQL workflows, Admin API data, lineage, and dbt documentation.

Use Cases

  • Ask Claude to inspect model lineage before changing a transformation.
  • Search dbt documentation from an agent workflow.
  • Review job runs, artifacts, or project metadata from dbt Platform.
  • Use SQL-oriented tools where credentials and approval flow are appropriate.

Safety and Privacy

Treat dbt MCP as access to your analytics operating context. It can surface model names, SQL, warehouse details, run artifacts, and platform metadata. Keep write or execution paths behind human approval until the workflow is tested.

Duplicate Check

No dedicated dbt MCP entry exists in content/mcp. This is distinct from generic data or orchestration tool listings.

References

#dbt#data-engineering#analytics#lineage#official

Source citations

Add this badge to your README

Show that dbt MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/dbt-mcp-server.svg)](https://heyclau.de/entry/mcp/dbt-mcp-server)

How it compares

dbt MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Field
dbt MCP Server

Official dbt Labs MCP server that gives AI agents context from dbt Core, dbt Fusion, dbt Platform, project metadata, SQL tools, lineage, Admin API, and dbt documentation search.

Open dossier
Anthropic logoGit MCP Server for Claude

Official MCP server providing Git repository tools for reading, searching, and manipulating Git repositories

Open dossier
GitHub logoGitHub MCP Server for Claude

Official GitHub MCP server providing comprehensive GitHub API access for repository management, file operations, and search functionality

Open dossier
LINE Bot MCP Server logoLINE Bot MCP Server

Official LINE MCP server that connects Claude and other AI agents to the LINE Messaging API for push messages, broadcasts, profile lookup, quotas, follower IDs, and rich-menu management.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustDiffersPackage not verifiedPackage verifiedPackage verifiedPackage not verified
Source provenanceDiffersSource-backedNo submission linkNo submission linkSource-backed
SubmitterDiffersJSONbored——oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand—Anthropic logoAnthropicGitHub logoGitHubLINE Bot MCP Server logoLINE Bot MCP Server
Categorymcpmcpmcpmcp
SourceSource-backedFirst-partyFirst-partySource-backed
Authordbt LabsAnthropicGitHubLINE
Added2026-06-052025-09-162025-09-182026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓SQL and admin tools can inspect or affect real analytics environments depending on credentials. Start with read-oriented docs and metadata tools before enabling execution paths.✓Restrict access to intended repositories and review write operations because commands can alter branches, commits, and working trees.✓Use a least-privilege GitHub token because repository, issue, pull request, and file operations can modify public or private projects.✓LINE Bot MCP Server can push text and flex messages to users, broadcast messages to all followers, retrieve follower IDs, inspect profiles, check message quotas, create rich menus, set default rich menus, cancel defaults, and delete rich menus. Broadcast and rich-menu tools can affect every user following the connected LINE Official Account, so require human approval before running them in production. Push-message tools can contact individual users directly; confirm the target `userId`, message body, and account context before sending. Rich-menu tools can upload generated menu images and change user-facing navigation for the account. Use least-privilege channel tokens where possible, keep test and production LINE accounts separate, and monitor quota consumption. The upstream README marks the project as a preview version for experimental use with potentially incomplete functionality or support.
Privacy notes✓dbt metadata, SQL, lineage, model names, run artifacts, and platform account details can expose private analytics structure.✓Source code, commit history, author metadata, file paths, and repository configuration may be sent through tool calls.✓Repository contents, issues, pull requests, comments, org metadata, and user details may be sent through model context.✓Channel access tokens, destination user IDs, follower IDs, profile display names, profile picture URLs, status messages, language, message contents, flex-message JSON, and rich-menu IDs can be exposed to the MCP client. Broadcast prompts, generated messages, user IDs, and profile results may be retained in MCP client logs, terminal history, model context, or chat transcripts. Treat LINE Official Account credentials and recipient identifiers as secrets, and avoid pasting real tokens or user IDs into shared logs. Review LINE platform policies and internal consent requirements before retrieving follower IDs or using AI-generated outbound messages.
Prerequisites
  • dbt project, dbt Core/Fusion environment, or dbt Platform account.
  • MCP client and credentials appropriate to the dbt features enabled.
  • Git installed (verify with: git --version, install via sudo apt install git (Linux) or brew install git (macOS))
  • Node.js and npx available (comes with Node.js, verify with: npx --version)
  • Local Git repository (server works with local repositories only, navigate to repository root directory)
  • File system read permissions for repository directory (check with ls -l or icacls)
  • GitHub account (sign up at https://github.com if needed)
  • GitHub Personal Access Token with repo scope (generate from GitHub Settings > Developer Settings > Personal Access Tokens)
  • Docker installed and running (verify with: docker --version)
  • Internet connection (remote GitHub API access required)
  • Node.js 22 or newer for the published npm package.
  • A LINE Official Account with the Messaging API enabled.
  • A LINE channel access token with the permissions needed for the intended tools.
  • A destination user ID when using the default recipient flow for push-message tools.
Install
Install from the dbt MCP repository or latest release assets according to the official README.
claude mcp list && claude mcp status git
claude mcp add github -e GITHUB_PERSONAL_ACCESS_TOKEN=YOUR_TOKEN -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server && claude mcp list
npx -y @line/line-bot-mcp-server
Config
{
  "mcpServers": {
    "dbt": {
      "command": "uvx",
      "args": ["dbt-mcp"]
    }
  }
}
{
  "mcpServers": {
    "git": {
      "args": [
        "-y",
        "@modelcontextprotocol/server-git"
      ],
      "command": "npx",
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "github": {
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}"
      },
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GITHUB_PERSONAL_ACCESS_TOKEN",
        "ghcr.io/github/github-mcp-server"
      ],
      "command": "docker",
      "type": "stdio"
    }
  }
}
Manual-only setup:
claude mcp add line-bot --env CHANNEL_ACCESS_TOKEN=YOUR_CHANNEL_ACCESS_TOKEN -- npx -y @line/line-bot-mcp-server
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Usage Analytics for Claude Code Team Rollout

Use Claude Code analytics to measure adoption during team rollouts.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.