Guides7 min read

Best MCP Servers for dbt Developers in 2026

dbt, Snowflake, BigQuery, data warehousing — these MCP servers give analytics engineers AI assistance that understands your actual data models, lineage, and warehouse.

By MyMCPTools Team·

Analytics engineers working with dbt occupy an interesting position: their code is SQL, but the engineering discipline looks a lot like software development. Data model lineage, test coverage, documentation, and incremental builds — these are software engineering concepts applied to data transformation.

AI assistance for dbt work fails when the AI doesn't know your actual schema, data model relationships, or warehouse configuration. These MCP servers give your AI the context it needs to be genuinely useful.

1. PostgreSQL MCP Server — Live Schema and Query Context

dbt models compile to SQL that runs against your warehouse. Whether you're developing locally with PostgreSQL, DuckDB, or connecting to Snowflake/BigQuery through a compatible interface, having your AI understand your actual schema is the foundation of useful assistance. The PostgreSQL MCP server gives your AI introspection access to your database schema — enabling accurate model writing and query generation.

Key capabilities:

  • Inspect source tables, materialized views, and dbt-created models
  • Understand column types, nullability, and constraints for accurate SQL generation
  • Query data for development and debugging
  • Analyze query performance (EXPLAIN plans)

Best for: Analytics engineers developing against a PostgreSQL target or using PostgreSQL as a local development environment (common with dbt Core). Your AI writing a model that joins three source tables produces accurate SQL when it can see those tables' actual schemas.

2. Filesystem MCP Server — dbt Project Navigation

A mature dbt project is a complex directory: models, tests, sources, macros, seeds, snapshots, and documentation. The filesystem MCP server gives your AI natural navigation of your dbt project structure — understanding not just individual model files but how the entire project is organized and cross-referenced.

Key capabilities:

  • Read model SQL files, YAML configurations, and schema definitions
  • Navigate the models/ directory tree (staging, marts, intermediate layers)
  • Access profiles.yml and dbt_project.yml for project context
  • Read custom macros and understand the macro library
  • Inspect packages.toml and installed dbt packages

Best for: All dbt developers. Your AI understanding your actual project structure — including how your models are layered (raw → staging → marts) and what macros are available — means suggestions match your project conventions rather than generic dbt examples.

3. GitHub MCP Server — PR Review and Model Lineage Tracking

dbt projects benefit enormously from version control discipline: every model change goes through a PR, breaking changes get flagged, and the data contract between model layers is documented in git history. The GitHub MCP server connects your AI to this PR workflow, enabling data-aware code review.

Key capabilities:

  • Review model changes in PRs for breaking schema changes
  • Track data contract changes across model versions
  • Search the project's git history for when a model was changed and why
  • Browse the dbt packages repository for reference implementations

Best for: Analytics engineering teams who treat their dbt project with the same rigor as a software codebase. Particularly valuable for reviewing PRs that modify widely-referenced staging models — your AI can identify all downstream models that might be affected by a column rename.

4. SQLite MCP Server — dbt Artifacts and Manifest Analysis

dbt generates rich artifacts after each run: manifest.json, run_results.json, and catalog.json. These files contain complete model lineage, test results, execution timing, and schema documentation. While dbt artifacts are JSON, many teams load them into SQLite or DuckDB for analysis. The SQLite MCP server enables your AI to query this run history directly.

Key capabilities:

  • Query model run history and execution timing
  • Analyze test failures across runs
  • Explore model lineage from artifact data
  • Track schema drift over time

Best for: Analytics engineering teams who build tooling around dbt artifacts. If you've loaded your manifest.json into SQLite or DuckDB for lineage analysis, your AI can query it directly to answer "which models depend on this source table?"

5. Brave Search MCP Server — dbt Ecosystem and Package Research

The dbt ecosystem evolves quickly: new packages, warehouse-specific best practices, dbt Core release notes, and community solutions to common problems. The Brave Search MCP server gives your AI current information about the dbt ecosystem — beyond its training data cutoff.

Key capabilities:

  • Find current dbt-utils, dbt-expectations, and other package documentation
  • Research warehouse-specific SQL syntax and optimizations
  • Look up current dbt Core release notes and breaking changes
  • Find community-vetted solutions for common dbt patterns

Best for: Analytics engineers evaluating dbt packages or working across multiple warehouses with different SQL dialects. "Find the current dbt-utils documentation for generate_surrogate_key" gets you accurate, current docs rather than outdated training data.

Recommended Stacks for dbt Developers

  • Solo analytics engineers: Filesystem + PostgreSQL (project navigation + schema context)
  • Analytics engineering teams: Filesystem + PostgreSQL + GitHub (full development workflow)
  • Platform-focused teams: Filesystem + GitHub + SQLite (project + version control + artifact analysis)
  • Full stack: All of the above — your AI understands the complete dbt project lifecycle

Browse all Database MCP servers on MyMCPTools. For related guides, see Best MCP Servers for Data Engineering and Best MCP Servers for Data Analysts.

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

📁

Filesystem

Secure file operations with configurable access controls. Read, write, and manage files safely.

Local
💻

GitHub MCP Server

The GitHub MCP server is GitHub's official Model Context Protocol integration, giving AI assistants like Claude and Cursor direct, authenticated access to the GitHub platform and its full developer surface. With this MCP server, you can ask your AI to read and write repository files, create and merge branches, open and review pull requests, comment on and close issues, trigger GitHub Actions workflows, search across code repositories with GitHub's code search, and inspect commit history — all through natural-language prompts in your AI interface. Developers use it to supercharge code review workflows, automate issue triage, generate PR descriptions from diffs, bulk-update repository settings, and wire AI agents into CI/CD pipelines. The GitHub MCP server connects via a GITHUB_PERSONAL_ACCESS_TOKEN environment variable with scopes for the operations you need, keeping authentication clean and auditable. Install with Docker: `docker run -e GITHUB_PERSONAL_ACCESS_TOKEN=<token> ghcr.io/github/github-mcp-server` — or configure it as a remote MCP server in Claude Desktop, Cursor, VS Code, Windsurf, and Cline. With over 8,000 GitHub stars, it is the most widely deployed official code-platform MCP server and the reference implementation for AI-native GitHub automation.

Auth required
🗄️

SQLite MCP Server

The SQLite MCP server is an official Anthropic reference implementation that gives AI assistants direct, conversational access to SQLite databases — the world's most widely deployed database engine. Through natural language, you can ask Claude or Cursor to run SELECT queries, insert and update rows, inspect table schemas, create new tables, and generate business intelligence reports without writing a single SQL statement manually. Common use cases include exploring local data files, prototyping application schemas, auditing CSV imports, running ad-hoc analytics on app databases, and letting AI agents manage lightweight structured storage during agentic workflows. The server exposes tools for query execution, schema introspection, and memo-style business insights that synthesize query results into readable summaries. It requires a path to an existing .db file as a startup argument. Install with: npx @modelcontextprotocol/server-sqlite /path/to/your-database.db. Works with Claude Desktop, Cursor, VS Code, and all MCP-compatible clients. For developers who want AI to reason directly over structured data stored locally, the SQLite MCP server is the fastest path from question to answer without leaving your AI chat interface.

Local
🔍

Brave Search MCP Server

The Brave Search MCP Server is the official server from Brave that gives AI assistants privacy-first web search through the independent Brave Search API — no tracking, no profiling, and results drawn from Brave's own web index rather than Google or Bing. It exposes five distinct tools that map directly to the Brave Search API endpoints: brave_web_search for general queries with pagination, freshness filters, and safe-search controls; brave_local_search for businesses, restaurants, and points of interest with automatic location filtering; brave_news_search for recent articles and current events; brave_image_search for image discovery; and brave_video_search for finding videos across the web. Authentication uses a single BRAVE_API_KEY (free tier available at brave.com/search/api) or a mounted BRAVE_API_KEY_FILE for Docker-secret setups. Install in Claude Desktop, Cursor, Windsurf, or VS Code with one npx command and choose stdio or streamable-HTTP transport. Because Brave operates its own crawler and index, the Brave Search MCP server is a strong choice for developers who want an alternative to Google-dependent search tools, need reproducible non-personalized results, or care about data privacy in agent workflows — Claude can pull fresh web context, verify facts, and research topics without leaking queries to ad-tech pipelines.

Local

📚 More from the Blog