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
Datadog MCP Server
Datadog documents a remote Model Context Protocol server at docs.datadoghq.com/bits_ai/mcp_server that connects AI agents in Cursor, Claude Code, Codex CLI, VS Code, Gemini CLI, and other MCP clients to observability data across APM, logs, metrics, monitors, dashboards, and security signals. Setup guides describe OAuth-based connection to Datadog's hosted MCP endpoint (distinct from the local-only Code Security MCP Server used for SAST/SCA scans). Fair-use limits listed in docs include 50 requests per 10 seconds burst and 50,000 monthly tool calls; Audit Trail records MCP actions with tool name, arguments, user identity, and client, while metrics `datadog.mcp.session.starts` and `datadog.mcp.tool.usage` tag usage by client and tool.
Mem0 MCP Server
Mem0 documents a hosted Model Context Protocol server at https://mcp.mem0.ai/mcp that exposes Platform memory tools (`add_memory`, `search_memories`, `get_memories`, `update_memory`, `delete_memory`, `delete_all_memories`, `delete_entities`, `list_entities`, `list_events`, `get_event_status`) to Claude, Claude Code, Codex, Cursor, Windsurf, VS Code, and OpenCode. Setup uses `npx mcp-add` with HTTP transport or manual JSON/TOML client configs; Codex requires `MEM0_API_KEY` as bearer token per docs.mem0.ai/platform/mem0-mcp. The cloud server needs a Mem0 Platform API key from the dashboard and Node.js for the installer—no local vector database required for the hosted path.
Apify MCP Server
Apify documents an official Model Context Protocol server hosted at https://mcp.apify.com that speaks Streamable HTTP in line with the current MCP specification; Apify warns that SSE transport was deprecated for removal April 1, 2026. Hosted clients authenticate through browser OAuth or by supplying Bearer tokens sourced from Console → Settings → Integrations (`APIFY_TOKEN`), can pin tool bundles via URL query (`?tools=actors,docs,apify/rag-web-browser` style examples reproduce Apify wording), optionally append `telemetry-enabled=false`, and benefit from inferred structured-output schemas surfaced for Actor tooling on hosted endpoints unlike the default stdio server. When MCP clients refuse remote transports, docs recommend `npx -y @apify/actors-mcp-server` with `APIFY_TOKEN` for stdio, Node.js ≥18, and adherence to documented per-user throughput (Apify cites up to thirty requests per second across Actor runs plus storage/documentation calls). Specialized payment modes (open x402 on Base plus Skyfire) appear as optional adjunct pages inside the broader integration handbook.