ConductorOne · mindymo · Jul 23, 2026 · Jul 16, 2026 · Jul 16, 2026 · Jul 16, 2026
diff --git a/docs.json b/docs.json
@@ -107,7 +107,8 @@
               {
                 "group": "MCP server setup guides",
                 "pages": [
-                  "product/admin/mcp-server/mcp-bridge",
+                  "product/admin//mcp-server/mcp-bridge",
+                  "product/admin/mcp-server/google-cloud-project-setup",
                   "product/admin/mcp-server/apollo",
                   "product/admin/mcp-server/auth0",
                   "product/admin/mcp-server/azure-devops",

diff --git a/product/admin/mcp-server/google-analytics-admin.mdx b/product/admin/mcp-server/google-analytics-admin.mdx
@@ -9,7 +9,7 @@
 {/* Editor Refresh: 2026-06-11 */}

 <Note>
 **Activation required.** AI access management must be enabled for your tenant before you can use it. To get started, [contact the C1 support team](mailto:support@c1.ai) for a walkthrough.
 </Note>

 The Google Analytics Admin MCP server lets you govern access to Google Analytics 4 configuration — accounts, properties, data streams, custom dimensions, conversions, and account-level user permissions — as tools your AI clients can call through C1.
@@ -30,7 +30,7 @@
 ## Before you begin
 
 - AI access management must be enabled for your tenant. See [Enable AI access management](/product/admin/enable-ai-access-management).
-- A Google Cloud project where you can enable the Google Analytics Admin API and create credentials.
+- A Google Cloud project, set up as described in [Set up a Google Cloud project for MCP servers](/product/admin/mcp-server/google-cloud-project-setup) (enable the Google Analytics Admin API, create OAuth credentials, and grant users the **Service Usage Consumer** role on the quota project).
 - The right GA4 role for the operations you need. Reads need at least **Viewer**, edits and creates need **Editor** at the property level or **Administrator** at the account level, and managing GA4 user permissions needs **Administrator** at the account level.
 
 <Note>
@@ -81,7 +81,7 @@
 Follow [Register an MCP server](/product/admin/mcp-servers#register-an-mcp-server) and select **Google Analytics Admin** from the catalog.
 </Step>
 <Step>
-When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose per-user OAuth and enter your OAuth client's **client ID** and **client secret**, plus the scopes you configured.
+When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose per-user OAuth and enter your OAuth client's **client ID** and **client secret**, plus the scopes you configured. Also enter the **Google Cloud Quota Project ID** — the ID of the project where you enabled the Google Analytics Admin API and granted users the Service Usage Consumer role.
 </Step>
 <Step>
 Save your changes. The first time a user calls a Google Analytics Admin tool from their AI client, they're prompted to connect their Google account.
@@ -139,7 +139,7 @@

 Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification).

 Before anyone can call a Google Analytics Admin tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up.

 <Note>
 Tool discovery runs even if your credentials are incorrect, so seeing discovered tools doesn't confirm that authentication is working. You confirm your Google Analytics Admin credentials when an approved user successfully calls a Google Analytics Admin tool from their AI client.

diff --git a/product/admin/mcp-server/google-analytics.mdx b/product/admin/mcp-server/google-analytics.mdx
@@ -9,10 +9,10 @@
 {/* Editor Refresh: 2026-06-11 */}

 <Note>
 **Activation required.** AI access management must be enabled for your tenant before you can use it. To get started, [contact the C1 support team](mailto:support@c1.ai) for a walkthrough.
 </Note>

 The Google Analytics MCP server lets you govern access to Google Analytics 4 report data — dimensions, metrics, realtime events, pivot reports, and audience exports — as tools your AI clients can call through C1.

 Google Analytics supports two ways to authenticate, and you choose one when you register the server:

@@ -30,7 +30,7 @@
 ## Before you begin
 
 - AI access management must be enabled for your tenant. See [Enable AI access management](/product/admin/enable-ai-access-management).
-- A Google Cloud project where you can enable the Google Analytics Data API and create credentials.
+- A Google Cloud project, set up as described in [Set up a Google Cloud project for MCP servers](/product/admin/mcp-server/google-cloud-project-setup) (enable the Google Analytics Data API, create OAuth credentials, and grant users the **Service Usage Consumer** role on the quota project).
 - Access to the GA4 properties you want to query. The user or service account must already have at least **Viewer** access on those properties.
 
 <Note>
@@ -77,7 +77,7 @@
 Follow [Register an MCP server](/product/admin/mcp-servers#register-an-mcp-server) and select **Google Analytics** from the catalog.
 </Step>
 <Step>
-When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose per-user OAuth and enter your OAuth client's **client ID** and **client secret**, plus the scopes you configured.
+When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose per-user OAuth and enter your OAuth client's **client ID** and **client secret**, plus the scopes you configured. Also enter the **Google Cloud Quota Project ID** — the ID of the project where you enabled the Google Analytics Data API and granted users the Service Usage Consumer role.
 </Step>
 <Step>
 Save your changes. The first time a user calls a Google Analytics tool from their AI client, they're prompted to connect their Google account.
@@ -135,7 +135,7 @@

 Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification).

 Before anyone can call a Google Analytics tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up.

 <Note>
 Tool discovery runs even if your credentials are incorrect, so seeing discovered tools doesn't confirm that authentication is working. You confirm your Google Analytics credentials when an approved user successfully calls a Google Analytics tool from their AI client.