dbt Labs documents an official Model Context Protocol server at docs.getdbt.com/docs/dbt-ai/about-mcp (repository dbt-labs/dbt-mcp) that exposes governed access to dbt project metadata, lineage, CLI actions, and dbt Platform APIs for Claude, Cursor, and custom MCP clients. Local mode runs via `uvx dbt-mcp` with environment variables such as DBT_PROJECT_DIR, DBT_HOST, DBT_TOKEN, DBT_PROD_ENV_ID, and DBT_USER_ID; remote mode connects over HTTP/SSE to a managed dbt Platform MCP endpoint with OAuth. Documented tool groups include product-doc search (`search_product_docs`, `get_product_doc_pages`) and server metadata helpers, with additional development and deployment tools synced from the GitHub README per release.
Use cases
- Give coding agents searchable access to docs.getdbt.com without manual copy-paste
- Expose dbt project lineage and metadata during refactors in Cursor
- Automate dbt CLI or Platform tasks from agent workflows with explicit env configuration
- Use remote MCP + OAuth when analysts should not install local uvx tooling
- Pair MCP doc tools with Snowflake or warehouse projects that publish dbt models
Key features
- Claude Desktop
- Claude Code
- Cursor
- Custom MCP clients
Frequently Asked Questions
- What is the difference between local and remote dbt MCP?
- Docs describe local uvx dbt-mcp on your machine versus HTTP remote endpoints hosted on dbt Platform with OAuth—remote suits consumption-heavy setups without local installs.
- Do I need a dbt Cloud account?
- Local mode can target dbt Core projects via DBT_PROJECT_DIR; Platform tokens (DBT_TOKEN, env IDs) unlock cloud metadata and remote server options per docs.
- Where is the tool list maintained?
- dbt docs state the public tool inventory is synced from the dbt-mcp GitHub README each release; check that README for the current set.
Related
Related
3 Indexed items
Algolia Productivity MCP Server
Algolia documents an official managed Model Context Protocol server at algolia.com/doc/guides/model-context-protocol/productivity-mcp. Connect MCP clients to the remote HTTP endpoint `https://mcp.algolia.com/mcp` with OAuth (enable under Generate AI in the Algolia dashboard; sign in when prompted so the MCP inherits your account permissions). Productivity MCP is user-scoped and read-only per docs—tools cover search (`algolia_search_list_indices`, `algolia_search_index`, `algolia_search_for_facet_values`), Recommend (`algolia_recommendations`), and analytics helpers such as top searches, no-click rates, filter usage, and user counts. Algolia docs distinguish this from Algolia Public MCP for application-scoped, curated index exposure to external agents. Supported clients include ChatGPT, Claude, Claude Code, Cursor, Gemini CLI, VS Code, and OpenAI Playground.
Neo4j MCP Server
Neo4j documents an official Model Context Protocol server at neo4j.com/docs/mcp/current and in the neo4j/mcp repository. It gives MCP clients structured access to a Neo4j graph: get-schema introspects labels, relationship types, and property keys; read-cypher runs read-only Cypher checked with EXPLAIN and Neo4j query-type classification; write-cypher runs writes unless NEO4J_MCP_READ_ONLY=true; list-gds-procedures lists Graph Data Science procedures when GDS is installed. Prerequisites are a running Aura, Neo4j Desktop, or self-managed database plus the APOC plugin. Local clients use stdio via uvx neo4j-mcp-server or the Homebrew/binary neo4j-mcp, with NEO4J_MCP_URI, NEO4J_MCP_USERNAME, NEO4J_MCP_PASSWORD, and NEO4J_MCP_DATABASE. Aura uses HTTP at https://<instance-id>.mcp-instances.neo4j.io after Tool authentication is enabled in the Aura console. Docs also describe an HTTP transport mode that takes URI and credentials per request and selects the database from the /db/{databaseName}/mcp path.
PostHog MCP Server
PostHog documents a free hosted Model Context Protocol endpoint at `https://mcp.posthog.com/mcp` per posthog.com/docs/model-context-protocol that lets MCP clients query analytics, manage feature flags, investigate errors, run HogQL, triage support workflows, and configure CDP destinations from natural-language prompts. The PostHog Wizard installs the server into Cursor, Claude Code, Claude Desktop, Codex, VS Code, Windsurf, and Zed via `npx @posthog/wizard@latest mcp add`. Authentication routes to the correct US or EU data region; manual setups can pass a personal API key with the MCP Server preset through `mcp-remote` and an `Authorization` Bearer header. Source lives in the PostHog monorepo at `services/mcp` (the standalone PostHog/mcp repository redirects there).