Skip to content

google-cloud-bigquery: add team OAuth client variables - #761

Merged
djiang-jq merged 2 commits into
mainfrom
cursor/bigquery-team-oauth-client-d351
Oct 22, 2026
Merged

djiang-jq merged 2 commits into
mainfrom
cursor/bigquery-team-oauth-client-d351

Conversation

@djiang-jq

@djiang-jq djiang-jq commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

Note

Medium Risk
Changes how users authenticate to BigQuery (team-supplied OAuth secrets) and is a breaking migration for existing installs, though scope is limited to plugin metadata and MCP config.

Overview
Bumps the Google Cloud BigQuery plugin to 1.1.0 and raises the minimum Cursor version to 3.19.0.

OAuth now uses a team-owned Google client instead of Cursor’s built-in client. The plugin declares required team variables CLIENT_ID and CLIENT_SECRET (secret is write-only/password), and mcp.json passes them through an auth block on the existing BigQuery MCP HTTP endpoint.

Docs and changelog describe admin setup in Google Cloud and the Cursor team plugin settings, note that existing installs must configure these values before the next connect, and that rotating the client signs members out.

Reviewed by Cursor Bugbot for commit 23bc01d. Bugbot is set up for automated code reviews on this repo. Configure here.

djiang-jq and others added 2 commits October 21, 2026 16:33
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@djiang-jq djiang-jq changed the title google-cloud-bigquery: add optional team OAuth client variables google-cloud-bigquery: add team OAuth client variables Oct 22, 2026
@djiang-jq
djiang-jq merged commit a3a6c05 into main Oct 22, 2026
2 checks passed
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