# dbt Labs MCP connector

The dbt Labs connector brings your dbt Labs users, groups, invites, warehouse connections and account audit history to Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client, with every request running as the signed-in person and logged.

Source: https://elaichi.ai/connectors/dbtlabs/

## Facts

| | |
| --- | --- |
| Application | dbt Labs |
| Category | BI |
| AI tools | 205 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once dbt Labs is connected

- Which dbt Labs users aren't in any group yet?
- List pending invites to our dbt Labs account.
- Who has permissions on the production warehouse connection?

## Connect dbt Labs in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick dbt Labs.
2. Optionally set Share with, then press Connect.
3. Paste a dbt Labs API key. One person generates a token in dbt Labs and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which dbt Labs tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## dbt Labs MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## dbt Labs MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## dbt Labs MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## dbt Labs MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## dbt Labs MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect dbt Labs to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a dbt Labs tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with dbt Labs through Elaichi

### Check who can reach the production warehouse

Data platform. Ask which groups hold permissions on each dbt Labs warehouse connection and which users sit in those groups, then tighten what needs tightening before the next review.

### Onboard a new analyst in one ask

IT. Send the dbt Labs invite, create or pick the right group, and assign the new hire to it without opening the admin console.

### Pull the audit log before a compliance check

Security. List recent dbt Labs account audit events and the IP restrictions in force, and get a plain summary of what changed and who changed it.

### Update a warehouse connection without a ticket

Analytics engineering. When credentials rotate or a host changes, update the dbt Labs connection details yourself and confirm the change took.

### Chase invites nobody accepted

Operations. See every open dbt Labs invite, how long it has been sitting, and who sent it, then follow up or resend.

### Reconcile seats ahead of renewal

Finance. List the users on each dbt Labs account and spot people who no longer need a seat before the invoice arrives.

## Elaichi vs Zapier MCP vs Composio for dbt Labs

All three can connect dbt Labs to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over dbt Labs tools | Allow or restrict single dbt Labs tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per dbt Labs call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect dbt Labs to Claude?

Connect dbt Labs in Elaichi first, which asks only for a dbt Labs API key, so there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and dbt Labs is available in your chat.

### Does dbt Labs work with ChatGPT and Cursor as well as Claude?

Yes. Once dbt Labs is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect dbt Labs once, not once per client.

### What can an AI agent actually do with my dbt Labs data?

It can list the users and groups on your dbt Labs account, send invites, assign people to groups, read the account audit log, check IP restrictions and view or update warehouse connections. Short, concrete asks such as "list open dbt Labs invites" work better than long sentences.

### Does connecting dbt Labs give the AI access to everything in my account?

No. Every request to dbt Labs runs with the access of the person who signed in to Elaichi, so an analyst who cannot edit connections in dbt Labs cannot edit them through an agent either. Elaichi can narrow that access further with restrictions, and it never widens it.

### Can my team share one dbt Labs connection?

Yes. One person connects dbt Labs with the API key and shares the connection with a team, and nobody else ever sees or handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every dbt Labs call.

### Can I stop an agent from deleting or changing things in dbt Labs?

Yes. Restrictions in Elaichi apply per action, so you can allow reading dbt Labs users and connections while restricting updates, invites or deleting a connection, on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it whatever the prompt says.

### What happens to a dbt Labs connection when someone leaves?

Offboarding that person in Elaichi ends their access to dbt Labs through every client at once. A shared dbt Labs connection keeps working for everyone else on the team. If you want the connection gone entirely, disconnecting dbt Labs once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the dbt Labs MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. dbt Labs is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for dbt Labs?

Yes. Both let Claude, ChatGPT or Cursor use dbt Labs. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every dbt Labs call.

### How is Elaichi different from Composio for dbt Labs?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to dbt Labs: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 205 dbt Labs tools

Every tool below is callable through https://api.elaichi.ai/mcp once dbt Labs is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all dbt Labs users** (List). List the dbt Cloud users associated with an account. Returns: id, created_at, updated_at. Required: account_id.
- **Get single dbt Labs user by ID** (Get). Get a single dbt Cloud user by id. Returns: id, created_at, updated_at. Required: account_id, id.
- **Update a dbt Labs user by ID** (Update). Update an existing dbt Cloud user by id. Returns the updated user record: id plus the user's schema-defined attributes. Required: id (integer user id) and a UserRequest JSON body.
- **List all dbt Labs accounts** (List). List the dbt accounts your API token is authorized to access. Returns: id, created_at, updated_at.
- **Get single dbt Labs account by ID** (Get). Get a single dbt Cloud account by its numeric id. Returns: id, created_at, updated_at. Required: id, account_id.
- **Dbt Labs accounts partial update** (Update). Partially update a dbt Labs account. Returns the updated account with its id, created_at, and updated_at. Required: account_id.
- **Update a dbt Labs account by ID** (Update). Update a dbt Labs account by id. Returns the updated account with its id, created_at, and updated_at. Required: id.
- **List all dbt Labs groups** (List). List groups in a dbt Labs account, filterable by name, primary key, and soft-deletion state. Returns: id, name, state, group_permissions. Required: account_id.
- **Get single dbt Labs group by ID** (Get). Get a single group in a dbt Labs account by id. Returns: id, name, state, group_permissions. Required: account_id and id.
- **Create a dbt Labs group** (Create). Create a group in a dbt Cloud account with a GroupRequest JSON body. Returns the created group object including its id, name, created_at, and updated_at. Required: account_id.
- **Update a dbt Labs group by ID** (Update). Update an existing group in a dbt Cloud account by id with a GroupRequest JSON body. Returns the updated group object including its id, name, created_at, and updated_at. Required: id, account_id.
- **Create a dbt Labs account assign group** (Create). Assign groups to a dbt account via a required request body that specifies the groups to assign. Returns the list of groups assigned to the account, including each group's id and name. Required: account_id.
- **List all dbt Labs account audit logs** (List). List dbt Cloud audit log events for an account. Returns a paginated collection of audit log event records with id and content-type-specific attributes. Required: account_id. Enterprise plans only.
- **List all dbt Labs account connections** (List). List all Account Connections in a dbt account. Returns: id, name, adapter_version, created_at. Required: account_id. Filter by adapter_version, name__icontains, private_endpoint_id, or the has_* feature flags.
- **Create a dbt Labs account connection** (Create). Create a new Account Connection in a dbt account. Returns: id, name, adapter_version, created_at. Required: account_id. Body fields are adapter-specific — use the adapter-schema endpoint to discover them.
- **Get single dbt Labs account connection by ID** (Get). Get a specific Account Connection in a dbt account by id. Returns: id, name, adapter_version, created_at. Required: id and account_id.
- **Update a dbt Labs account connection by ID** (Update). Update an existing Account Connection in a dbt account by id. Returns: id, name, adapter_version, created_at. Required: id and account_id. Body fields are adapter-specific — use the adapter-schema endpoint to discover them.
- **Delete a dbt Labs account connection by ID** (Delete). Delete an Account Connection in a dbt account by id. Returns an empty 204 response on success. Requires id and account_id.
- **List all dbt Labs account favorite assets** (List). List the favorite assets in a dbt account. Returns each favorited asset with its id and the environment_id, project_id, and user_id it is associated with. Required: account_id.
- **Create a dbt Labs account group permission** (Create). Set the permissions for a group in a dbt Cloud account. Returns the saved group permission payload as JSON; its fields are not enumerated in the available dbt API documentation. Required: account_id, group_permission_id, group_id, and a JSON request body (GroupPermissionListRequest).
- **List all dbt Labs account invites** (List). List invites for a dbt account. Returns: id, attributes (invite fields defined by dbt's Invite schema; the docs do not enumerate them). Required: account_id.
- **Create a dbt Labs account invite** (Create). Send email invites to users to add them to a dbt account. Returns: id, attributes (fields defined by dbt's InviteUsersResponse schema). Required: account_id and the invite request body.
- **Get single dbt Labs account invite by ID** (Get). Get an invite by id for a dbt account. Returns: id, attributes (invite fields defined by dbt's Invite schema; the docs do not enumerate them). Required: account_id and id.
- **List all dbt Labs account IP restrictions** (List). List the ip restriction rules configured for a dbt Cloud account. Returns ip restriction rules including id, created_at, and updated_at. Required: account_id.
- **Create a dbt Labs account IP restriction** (Create). Save a new ip restriction rule for a dbt Cloud account. Returns the created rule including id, created_at, and updated_at. Required: account_id. A 2XX is returned as long as at least one cidr saves successfully.
- **Get single dbt Labs account IP restriction by ID** (Get). Get a single ip restriction rule by id for a dbt Cloud account. Returns the rule including id, created_at, and updated_at. Required: account_id and id.
- **Update a dbt Labs account IP restriction by ID** (Update). Update an existing IP restriction rule in dbt by id. Returns the updated rule with its id, cidrs, and extra listing any CIDRs that failed to save. Required: account_id, id.
- **Delete a dbt Labs account IP restriction by ID** (Delete). Delete an IP restriction rule from a dbt account by id. Returns an empty 204 response on success. Required: account_id, id.
- **Create a dbt Labs account IP restrictions set** (Create). Toggle the enablement of the IP restriction feature for a dbt Cloud account. Returns the resulting IP restriction rule set object (dbt's IPRestrictionRuleSetEnveloped schema; its fields are not enumerated in the source docs). Required: account_id and a JSON request body.
- **List all dbt Labs account license maps** (List). List license maps for a dbt Cloud account. Returns license map records with id and attributes. Required: account_id. Only active records are returned by default.
- **Create a dbt Labs account license map** (Create). Create a license map in a dbt Cloud account. Returns the created license map record with id and attributes. Required: account_id. The request body follows the upstream LicenseMapRequest schema.
- **Get single dbt Labs account license map by ID** (Get). Get a single license map for a dbt Cloud account by id. Returns the license map record with id and attributes. Required: account_id and id.
- **Update a dbt Labs account license map by ID** (Update). Update a license map for a dbt Cloud account by id. Returns the updated license map record with id and attributes. Required: account_id, id. The request body follows the upstream LicenseMapRequest schema.
- **Delete a dbt Labs account license map by ID** (Delete). Delete a license map from a dbt Cloud account by id. Returns an empty 204 response on success. Required: account_id and id.
- **List all dbt Labs account oauth configurations** (List). List OAuth configurations for a dbt Cloud account. Returns each configuration's id, account_id, client_id, type, and state. Filter by client_id, type, or soft-deletion state (defaults to active); results order by id by default. Required: account_id.
- **Create a dbt Labs account oauth configuration** (Create). Create an OAuth configuration for a dbt Cloud account. Returns: id, account_id, client_id, type. Required: account_id. The request body follows the OAuthConfigurationRequest schema; its fields are not enumerated in the dbt API docs.
- **Get single dbt Labs account oauth configuration by ID** (Get). Get an OAuth configuration of a dbt Cloud account by id. Returns: id, account_id, client_id, type. Required: account_id, id.
- **Update a dbt Labs account oauth configuration by ID** (Update). Update an OAuth configuration of a dbt Cloud account by id. Returns: id, account_id, client_id, type. Required: account_id, id. The request body follows the OAuthConfigurationRequest schema; its fields are not enumerated in the dbt API docs.
- **Delete a dbt Labs account oauth configuration by ID** (Delete). Delete an OAuth configuration from a dbt Cloud account by id. Returns an empty 204 response on success. Required: id and account_id.
- **List all dbt Labs account private endpoints** (List). List all Private Endpoints for a dbt account, filterable by search term and endpoint type. Returns: pl_endpoint_ksuid, name, type, private_link_endpoint. Required: account_id.
- **Create a dbt Labs account private endpoint** (Create). Create a new Private Endpoint in a dbt account. Returns an empty response on success. Required: account_id.
- **Dbt Labs account private endpoints bulk update** (Update). Update an existing Private Endpoint in a dbt account, addressed by its KSUID identifier. Returns an empty response on success. Required: account_id, pl_endpoint_ksuid.
- **Dbt Labs account private endpoints bulk delete** (Delete). Delete a Private Endpoint from a dbt account, addressed by its KSUID identifier. Returns an empty 204 response on success. Required: account_id, pl_endpoint_ksuid.
- **List all dbt Labs account private endpoints private endpoints** (List). Retrieve the details of a specific Private Endpoint in dbt. Returns the endpoint record with its id and attributes (fields are defined upstream in the PrivateEndpointDetailResponse schema). Required: account_id, pl_endpoint_ksuid.
- **List all dbt Labs account projects** (List). List dbt Cloud projects in an account. Returns: id, name, state, created_at, updated_at, plus repository, connection, group_permissions, docs_job, or freshness_job when include_related is set. Required: account_id. Active projects only by default.
- **Create a dbt Labs account project** (Create). Create a dbt Cloud project in an account. Returns the created project: id, name, state, created_at, updated_at. Required: account_id and a project request body.
- **Get single dbt Labs account project by ID** (Get). Get a single dbt Cloud project by id. Returns: id, name, state, created_at, updated_at, plus repository, connection, group_permissions, docs_job, or freshness_job when include_related is set. Required: account_id and id.
- **Update a dbt Labs account project by ID** (Update). Update a dbt Cloud project by id with a JSON request body. Returns the updated project: id, name, state, created_at, updated_at. Required: account_id and id.
- **Delete a dbt Labs account project by ID** (Delete). Delete a dbt Cloud project by id. Returns an empty 204 response on success. Required: id and account_id. Deleted projects remain listable with state=deleted.
- **List all dbt Labs account projects accounts** (List). List dbt Cloud projects in an account. Returns each project with its id, name, state, created_at, and updated_at. Deprecated: dbt recommends using the v3 API instead. Required: account_id.
- ...and 155 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
