[djiang-jq]

Summary

The Google Cloud BigQuery plugin was set up for sign-in with nothing to configure. That can't work: Google's OAuth server doesn't support Dynamic Client Registration, so users have to bring their own OAuth client. This change asks for an OAuth Client ID and Client Secret, matching the BigQuery connector UI.

• plugin.json: adds required CLIENT_ID and CLIENT_SECRET variables. The secret is a password field (writeOnly, format: password). Bumps the plugin to 1.1.0.
• mcp.json: passes both values in auth and requests https://www.googleapis.com/auth/bigquery, the only scope listed in the server's protected resource metadata (/.well-known/oauth-protected-resource/mcp).
• README.md: adds setup steps: create a Web application OAuth client in Google Cloud, register the desktop (http://localhost:8787/callback) and web (https://www.cursor.com/agents/mcp/oauth/callback) redirect URIs, then enter the credentials in the plugin settings.
• CHANGELOG.md: adds a 1.1.0 entry.

The service-account option isn't included. The plugin still only signs in with each user's own Google account.

Test plan

• node scripts/validate-plugins.mjs
• Create a Google Cloud OAuth client, install the plugin, sign in, and list datasets

Made with Cursor

---

Note

Medium Risk
Changes how users authenticate to BigQuery MCP and requires storing OAuth client secrets in plugin configuration, though it follows the same BYO-OAuth pattern as other integration plugins.

^{Reviewed by Cursor Bugbot for commit 1f8ee6d. Bugbot is set up for automated code reviews on this repo. Configure here.}