docs: add Google Cloud project setup guide for MCP servers#395
Open
leet-c1 wants to merge 4 commits into
Open
Conversation
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>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
…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>
- 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>
Contributor
|
We want this to live in a general project setup guide for some of our MCP implementations. Since this shows up right next the vendors guide list, this is not specific to one vendor this is a general guide for how to setup a GCP project before using anything within the scope of its ecosystem (google calendar, cloud and other APIs etc). @mindymo I will leave it to you to decide. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a shared Google Cloud project setup guide for the Google MCP servers, and wires the existing Google connector pages to it.
product/admin/mcp-server/google-cloud-project-setup.mdx— one guide every Google MCP server shares. Covers:PERMISSION_DENIED,SERVICE_DISABLED, redirect-URI mismatch, restricted-scope verification)docs.json.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.docs.jsonvalidated as JSON.<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
mint broken-linksalso 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