Cursor plugin specification and official plugins
TypeScript
google-cloud-bigquery: add optional team OAuth client variables
djiang-jq017da53ffe3e
diff --git a/third_party/google-cloud-bigquery/.cursor-plugin/plugin.json b/third_party/google-cloud-bigquery/.cursor-plugin/plugin.jsonindex 37ffa283..59a3a8e5 100644--- a/third_party/google-cloud-bigquery/.cursor-plugin/plugin.json+++ b/third_party/google-cloud-bigquery/.cursor-plugin/plugin.json@@ -1,9 +1,9 @@{"name": "google-cloud-bigquery","displayName": "Google Cloud BigQuery",- "version": "1.0.0",+ "version": "1.1.0","minClientVersions": {- "cursor": "3.13.0"+ "cursor": "3.19.0"},"description": "Explore datasets and tables and run SQL queries.","author": {@@ -32,5 +32,22 @@"sql","mcp"],+ "variables": {+ "type": "object",+ "additionalProperties": false,+ "properties": {+ "CLIENT_ID": {+ "type": "string",+ "title": "Client ID",+ "description": "Optional. A Google OAuth client your team created, shared by every member. Leave empty to use Cursor's client."+ },+ "CLIENT_SECRET": {+ "type": "string",+ "title": "Client secret",+ "writeOnly": true,+ "format": "password"+ }+ }+ },"mcpServers": "./mcp.json"}diff --git a/third_party/google-cloud-bigquery/CHANGELOG.md b/third_party/google-cloud-bigquery/CHANGELOG.mdindex 1789565c..36a35062 100644--- a/third_party/google-cloud-bigquery/CHANGELOG.md+++ b/third_party/google-cloud-bigquery/CHANGELOG.md@@ -2,6 +2,10 @@All notable changes to this plugin will be documented here.+## 1.1.0++- Added optional `CLIENT_ID` and `CLIENT_SECRET` team variables so a team admin can set one shared Google OAuth client for every member. Leaving them empty keeps signing in with Cursor's client. Requires Cursor 3.19.0 or later.+## 1.0.0 — initial release- Added the `google-cloud-bigquery` MCP server pointing at Google Cloud BigQuery's hosted Streamable HTTP endpoint (`https://bigquery.googleapis.com/mcp`).diff --git a/third_party/google-cloud-bigquery/README.md b/third_party/google-cloud-bigquery/README.mdindex bedfbfe1..928bd4c5 100644--- a/third_party/google-cloud-bigquery/README.md+++ b/third_party/google-cloud-bigquery/README.md@@ -19,13 +19,26 @@ Or run `/add-plugin google-cloud-bigquery` in chat."mcpServers": {"google-cloud-bigquery": {"type": "http",- "url": "https://bigquery.googleapis.com/mcp"+ "url": "https://bigquery.googleapis.com/mcp",+ "auth": {+ "CLIENT_ID": "${CLIENT_ID:-}",+ "CLIENT_SECRET": "${CLIENT_SECRET:-}"+ }}}}```-Auth is OAuth. Cursor prompts for Google Cloud BigQuery sign-in when the plugin connects — there is no client ID or personal access token to configure.+Auth is OAuth. Cursor prompts for Google Cloud BigQuery sign-in when the plugin connects. By default it signs in with Cursor's Google OAuth client, so there is nothing to configure. A team can use its own client instead; see below.++## Use your team's own OAuth client++A team admin can have every member sign in under one Google OAuth client the team owns, so consent and audit show the team's own app.++1. In the Google Cloud console, create an OAuth client for a **Web application** and add Cursor's OAuth callback URL as an authorized redirect URI. Add the `https://www.googleapis.com/auth/bigquery` scope to the project's OAuth consent screen.+2. In the Cursor dashboard, open the team's plugin settings for **Google Cloud BigQuery** and enter the **Client ID** and **Client secret**.++Members then sign in to BigQuery under that client. The secret is stored encrypted and stays on Cursor's backend; it is never sent to members' machines. Leave both fields empty to use Cursor's client. Changing the client signs members out, and they reconnect once.## Before you connectdiff --git a/third_party/google-cloud-bigquery/mcp.json b/third_party/google-cloud-bigquery/mcp.jsonindex 4068482c..754fa58a 100644--- a/third_party/google-cloud-bigquery/mcp.json+++ b/third_party/google-cloud-bigquery/mcp.json@@ -2,7 +2,11 @@"mcpServers": {"google-cloud-bigquery": {"type": "http",- "url": "https://bigquery.googleapis.com/mcp"+ "url": "https://bigquery.googleapis.com/mcp",+ "auth": {+ "CLIENT_ID": "${CLIENT_ID:-}",+ "CLIENT_SECRET": "${CLIENT_SECRET:-}"+ }}}}