Google Cloud BigQuery MCP connector: OAuth redirect_uri_mismatch (Error 400)
Resolved 💬 3 comments Opened May 25, 2026 by JoyArchivist Closed Jun 28, 2026
Environment
- Claude Code (CLI), macOS (Darwin 25.5.0)
- Model: Opus 4.7 (1M context)
- Connector:
claude.ai Google Cloud BigQuery(claudeai-proxy → https://bigquery.googleapis.com/mcp)
Steps to reproduce
- From an active Claude Code session, run
/mcp - Select
claude.ai Google Cloud BigQuery - Choose authenticate / connect
- Browser opens to Google OAuth consent
- Sign in with a Google Workspace account
Expected
OAuth flow completes and the connector's data tools (queries, dataset listing) become available in the session.
Actual
Google returns:
Error 400: redirect_uri_mismatch Request details: flowName=GeneralOAuthFlow
The redirect URI the connector sends is not registered on the OAuth client Google is matching against.
Notes
- The two visible tools on the connector are
authenticateandcomplete_authentication. Theauthenticatetool, when called from inside a session, returns "Ask the user to run /mcp and select '…' to authenticate" — so the flow is intended to be driven entirely by the/mcpUI. - Calling
authenticateis not the failure point; the failure is on Google's side after the consent screen attempt, suggesting the connector's registered redirect URI is wrong (or scoped to a different OAuth client than the one being invoked). - The
Google_Compute_Engineconnector exposes the sameauthenticate/complete_authenticationpair — untested but likely affected if it shares the same OAuth client config. - Gmail / Calendar / Drive connectors on the same account work fine, so it's not an account-level issue.
Workaround
None inside Claude Code. Falling back to bq CLI with gcloud ADC.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗