Skip to content

docs: add Google Cloud project setup guide for MCP servers#395

Open
leet-c1 wants to merge 4 commits into
mainfrom
lee/google-cloud-project-mcp-setup
Open

docs: add Google Cloud project setup guide for MCP servers#395
leet-c1 wants to merge 4 commits into
mainfrom
lee/google-cloud-project-mcp-setup

Conversation

@leet-c1

@leet-c1 leet-c1 commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

What

Adds a shared Google Cloud project setup guide for the Google MCP servers, and wires the existing Google connector pages to it.

  • New page product/admin/mcp-server/google-cloud-project-setup.mdx — one guide every Google MCP server shares. Covers:
    • Creating/selecting a project and enabling billing
    • A per-connector "enable these APIs" table (Drive, Docs, Sheets, Slides, Gmail, Calendar, Contacts/People, Tasks, Chat, Meet, Forms, Drive Activity)
    • Granting users the Service Usage Consumer role on the quota project — the step that makes per-user OAuth work
    • OAuth consent screen (Internal vs External + restricted-scope verification), OAuth client + redirect URI
    • An optional service-account path
    • A troubleshooting table (PERMISSION_DENIED, SERVICE_DISABLED, redirect-URI mismatch, restricted-scope verification)
  • Nav: added the page to the MCP servers group in docs.json.
  • Wired existing pages: Google Drive, Google Analytics, and Google Analytics Admin now link the setup guide as a prerequisite and call out the quota-project grant + Quota Project ID field they previously omitted.

Why

The existing Google MCP server pages explain enabling the API and creating an OAuth client, but not the quota project dimension. With per-user OAuth, each user is the caller Google checks, and without the Service Usage Consumer role on the quota project their tool calls fail with PERMISSION_DENIED. This guide captures that once, cross-connector, instead of repeating it per page.

Testing

  • mint broken-links — none of the files in this PR are flagged; all internal links and in-page anchors resolve.
  • In-page anchors verified against generated heading slugs; docs.json validated as JSON.
  • Style checked against the docs-writing guide (descriptive sentence-case headings, intro before every <Steps>, action-led opener, root-relative links).
  • check-ui-labels.py — C1 UI labels (Project ID, per-user OAuth, Grant access, Domain-wide delegation, Add new, JSON key) match the frontend; remaining bold labels are Google Cloud Console UI (external, expected).

Notes / out of scope

  • Only the three Google connectors currently in the catalog (Drive, Analytics, Analytics Admin) are wired. The "enable these APIs" table already covers the wider Workspace set for when those connector pages land.
  • mint broken-links also surfaced pre-existing parse/link issues in unrelated files (developer/error-codes.mdx, rap/cel-expressions/env-user-attribute.md, and a few /docs/-prefixed links) that are not touched here — happy to address separately.

🤖 Generated with Claude Code

Add a shared setup guide covering project creation, enabling per-connector
APIs, the Service Usage Consumer grant that per-user OAuth requires on the
quota project, OAuth client creation, and a service-account option.

Wire the existing Google MCP server pages (Drive, Analytics, Analytics
Admin) to the guide and call out the quota-project grant they previously
omitted — the missing grant caused per-user tool calls to fail with
PERMISSION_DENIED.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
conductorone 🟢 Ready View Preview Jul 16, 2026, 10:25 PM

@mintlify

mintlify Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
conductorone 🟡 Building Jul 16, 2026, 10:24 PM

…copes

Expand the Google Cloud project setup guide with the concrete reference
needed to actually provision a project: the API service ID for each
connector plus gcloud commands to enable and list them, and a per-connector
OAuth scope reference (collapsible) covering Drive, Docs, Sheets, Slides,
Gmail, Calendar, Contacts, Tasks, Forms, Drive Activity, Meet, and Chat.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
leet-c1 and others added 2 commits July 16, 2026 22:42
- Add Google Analytics and Google Analytics Admin to the API/service-ID
  table, the gcloud enable example, and the OAuth scopes reference, so the
  page covers what the linked Analytics connector pages point to.
- Add a "Before you begin" prerequisites section.
- Tag the two plain code blocks as text.
- Add "Google hasn't verified this app" / test-user guidance (consent-screen
  note + troubleshooting row).
- Note that connectors without a dedicated page use the standard register
  flow; soften the billing step; note scope changes require reconnect;
  rename the troubleshooting heading.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant