Connect to Google Cloud changedthird-party/claude-desktop/connectors-google-cloud
Nearest release: v2.1.274, published an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 16 Sep 2026 21:29 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+37added
Lines−41removed
From line
10
where the diff opens
First seen
16 Sep 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 10, old and new numbered
/
from line 10
1010
1111## Set up the BigQuery server
1212
13<Steps>
14 <Step title="Prepare the Google Cloud project">
15 In the Google Cloud project that holds your BigQuery data, enable the BigQuery MCP server and grant each user the **MCP Tool User** role (`roles/mcp.toolUser`) together with the BigQuery roles their queries need. Google's [Use the BigQuery MCP server](https://docs.cloud.google.com/bigquery/docs/use-bigquery-mcp) guide covers both.
16 </Step>
13**1. Prepare the Google Cloud project**
1714
18 <Step title="Create a Desktop-app OAuth client in Google Cloud">
19 If the project has no OAuth consent screen, configure one first in the Google Cloud Console under **APIs & Services → OAuth consent screen**. Choose the **Internal** user type when all users are in your Google Workspace organization. With **External**, add every user as a test user while the app is in testing, or Google blocks their sign-in.
15In the Google Cloud project that holds your BigQuery data, enable the BigQuery MCP server and grant each user the **MCP Tool User** role (`roles/mcp.toolUser`) together with the BigQuery roles their queries need. Google's [Use the BigQuery MCP server](https://docs.cloud.google.com/bigquery/docs/use-bigquery-mcp) guide covers both.
2016
21 Then open **APIs & Services → Credentials**, choose **Create credentials → OAuth client ID**, and select **Desktop app** as the application type. When Google shows the new client, copy its **Client ID** (ends in `.apps.googleusercontent.com`) and **Client secret** (begins with `GOCSPX-`). You don't add redirect URIs, because Desktop-app clients accept loopback redirects automatically.
22 </Step>
17**2. Create a Desktop-app OAuth client in Google Cloud**
2318
24 <Step title="Add the server in the Enterprise Admin Console">
25 In the Enterprise Admin Console ([claude.ai](https://claude.ai) → **Organization settings**), open the **Connectors** page under **Desktop 3P**. Under **Managed MCP servers**, click **Add → Blank** and fill in the entry:
19If the project has no OAuth consent screen, configure one first in the Google Cloud Console under **APIs & Services → OAuth consent screen**. Choose the **Internal** user type when all users are in your Google Workspace organization. With **External**, add every user as a test user while the app is in testing, or Google blocks their sign-in.
2620
27 | Field | Value |
28 | - | - |
29 | **Name** | `BigQuery` |
30 | **Transport** | **Streamable HTTP** |
31 | **URL** | `https://bigquery.googleapis.com/mcp` |
32 | **OAuth** | **Bring your own client** |
33 | **Client ID** | The client ID from step 2 |
34 | **Client secret** | The client secret from step 2 |
35 | **Authorization server** | `["https://accounts.google.com"]` |
21Then open **APIs & Services → Credentials**, choose **Create credentials → OAuth client ID**, and select **Desktop app** as the application type. When Google shows the new client, copy its **Client ID** (ends in `.apps.googleusercontent.com`) and **Client secret** (begins with `GOCSPX-`). You don't add redirect URIs, because Desktop-app clients accept loopback redirects automatically.
3622
37 <Frame caption="A BigQuery entry on the Connectors page with OAuth set to Bring your own client.">
38 <img src="https://mintcdn.com/claude-ai/l0HgWAJ4dDJ1-I-u/images/third-party/admin-console-managed-mcp-oauth.png?fit=max&auto=format&n=l0HgWAJ4dDJ1-I-u&q=85&s=efa91a216efb8f99c1e4aefc0ed5b16a" alt="Managed MCP server entry named BigQuery in the Enterprise Admin Console, with Transport set to Streamable HTTP, the BigQuery MCP URL, OAuth set to Bring your own client, and the Client ID, Client secret, and Authorization server fields filled in." width="1952" height="1705" data-path="images/third-party/admin-console-managed-mcp-oauth.png" />
39 </Frame>
23**3. Add the server in the Enterprise Admin Console**
4024
41 Click **Save changes**. Users' apps pick up the new entry as described under [Configuration updates](/docs/third-party/claude-desktop/admin-console#configuration-updates). Devices need outbound HTTPS access to `bigquery.googleapis.com`, `accounts.google.com`, and `oauth2.googleapis.com`.
25In the Enterprise Admin Console ([claude.ai](https://claude.ai) → **Organization settings**), open the **Connectors** page under **Desktop 3P**. Under **Managed MCP servers**, click **Add → Blank** and fill in the entry:
4226
43 If you manage configuration through MDM or a bootstrap server instead, the equivalent [`managedMcpServers`](/docs/third-party/claude-desktop/configuration#managedmcpservers) entry is:
27| Field | Value |
28| - | - |
29| **Name** | `BigQuery` |
30| **Transport** | **Streamable HTTP** |
31| **URL** | `https://bigquery.googleapis.com/mcp` |
32| **OAuth** | **Bring your own client** |
33| **Client ID** | The client ID from step 2 |
34| **Client secret** | The client secret from step 2 |
35| **Authorization server** | `["https://accounts.google.com"]` |
4436
45 ```json theme={null}
46 {
47 "name": "BigQuery",
48 "transport": "http",
49 "url": "https://bigquery.googleapis.com/mcp",
50 "oauth": {
51 "clientId": "CLIENT_ID.apps.googleusercontent.com",
52 "clientSecret": "GOCSPX-YOUR_CLIENT_SECRET",
53 "authorizationServer": ["https://accounts.google.com"]
54 }
55 }
56 ```
57 </Step>
37
5838
59 <Step title="Have users connect">
60 Each user opens **Customize → Connectors** in Claude Desktop, clicks **Connect** next to **BigQuery**, and approves Google's consent screen in the browser. Claude Desktop asks Google for offline access automatically, so the token refreshes in the background without another sign-in.
61 </Step>
62</Steps>
39Click **Save changes**. Users' apps pick up the new entry as described under [Configuration updates](/docs/third-party/claude-desktop/admin-console#configuration-updates). Devices need outbound HTTPS access to `bigquery.googleapis.com`, `accounts.google.com`, and `oauth2.googleapis.com`.
40
41If you manage configuration through MDM or a bootstrap server instead, the equivalent [`managedMcpServers`](/docs/third-party/claude-desktop/configuration#managedmcpservers) entry is:
42
43```json theme={null}
44{
45 "name": "BigQuery",
46 "transport": "http",
47 "url": "https://bigquery.googleapis.com/mcp",
48 "oauth": {
49 "clientId": "CLIENT_ID.apps.googleusercontent.com",
50 "clientSecret": "GOCSPX-YOUR_CLIENT_SECRET",
51 "authorizationServer": ["https://accounts.google.com"]
52 }
53}
54```
55
56**4. Have users connect**
57
58Each user opens **Customize → Connectors** in Claude Desktop, clicks **Connect** next to **BigQuery**, and approves Google's consent screen in the browser. Claude Desktop asks Google for offline access automatically, so the token refreshes in the background without another sign-in.
6359
6460## Other Google servers
6561
No line in this hunk matches that.