docs/features/feature-guides/ask-datahub-plugins/bigquery.md
import FeatureAvailability from '@site/src/components/FeatureAvailability';
Note: Ask DataHub Plugins is currently in Private Beta. To enable this feature, please reach out to your DataHub customer support representative.
The BigQuery Plugin connects Ask DataHub to Google BigQuery via the BigQuery MCP server, enabling conversational analytics directly from the chat. Like the Snowflake and Databricks plugins, DataHub acts as the semantic layer — finding the right data — while BigQuery serves as the data layer — executing queries and returning results.
With the BigQuery plugin enabled, Ask DataHub can:
Because the plugin uses Google OAuth, each user authenticates with their own Google account. Users only see data they are authorized to access via IAM — no need to manage separate policies in DataHub.
Example prompts:
roles/bigquery.dataViewer, roles/bigquery.jobUser, and roles/mcp.toolUser)The BigQuery plugin uses User OAuth authentication — each user authenticates with their own Google account. Setup involves enabling the BigQuery MCP server, creating an OAuth client in Google Cloud, then configuring the plugin in DataHub.
Enable the BigQuery MCP server in your Google Cloud project using the gcloud CLI:
gcloud beta services mcp enable bigquery.googleapis.com \
--project=YOUR_PROJECT_ID
:::tip gcloud version
This command requires a recent version of the gcloud CLI beta component. If you see Invalid choice: 'mcp', run gcloud components update to update to the latest version.
:::
For more details, see the Google Cloud documentation.
Create a Web application OAuth client in Google Auth Platform > Clients. When configuring the client, add your DataHub OAuth callback URL as an Authorized redirect URI:
https://<your-datahub-url>/integrations/oauth/callback
:::caution Redirect URI
The Authorized redirect URI must match the OAuth Callback URL shown in the DataHub plugin creation form exactly (e.g. https://your-org.acryl.io/integrations/oauth/callback). You can copy this URL from the DataHub form when creating the plugin in Step 3.
:::
After creating the client, copy the Client ID and Client Secret immediately — the client secret won't be shown again.
<p align="center"> </p>For detailed instructions, see Obtain OAuth 2.0 credentials in the Google documentation.
| Field | Value |
|---|---|
| Name | BigQuery |
| Description | A description for the plugin |
| MCP Server URL | https://bigquery.googleapis.com/mcp |
| Authentication Type | User OAuth (Each user authenticates) |
| Field | Value |
|---|---|
| Client ID | From Step 2 |
| Client Secret | From Step 2 |
| Default Scopes | https://www.googleapis.com/auth/bigquery |
:::info OAuth Scopes
The https://www.googleapis.com/auth/bigquery scope grants read and write access to BigQuery. For a full list of available scopes, see BigQuery OAuth scopes.
:::
Navigate to Settings > My AI Settings, find the BigQuery plugin, and click Connect. You'll be redirected to Google to authenticate, then back to DataHub. See the overview for more details.
:::note OAuth Consent Screen If your OAuth consent screen is set to Internal, only users within your Google Workspace organization can authenticate. If set to External and not yet verified, users may see a warning — they can proceed by clicking Advanced > Go to <app name>. For production use, consider verifying the consent screen. :::
Once connected, Ask DataHub can use the BigQuery MCP server to:
For the full list of available tools, see the BigQuery MCP reference.
execute_sql queries are limited to 3 minutes by default — longer queries are canceled automatically