Skip to content

Remove Google MCP entries from small-business plugin#240

Open
localden wants to merge 1 commit into
mainfrom
den/remove-small-business-google-mcp
Open

Remove Google MCP entries from small-business plugin#240
localden wants to merge 1 commit into
mainfrom
den/remove-small-business-google-mcp

Conversation

@localden
Copy link
Copy Markdown
Contributor

What

Removes the gmail, google calendar, and google drive MCP server entries from small-business/.mcp.json.

Why

The Google-hosted MCP endpoints at *.googleapis.com use Google's OAuth server, which does not support dynamic client registration. Connecting requires a pre-registered OAuth client_id, and there is currently no client_id available for this plugin to use, so connections from this plugin to these endpoints cannot complete.

This brings small-business in line with the other plugins in this repo, which had the same entries removed in #184 for the same reason. The small-business plugin was added after #184 and reintroduced them.

Users can still connect Gmail, Calendar, and Drive through the Connectors Directory in the app, which is a separate connection path with its own authentication handling and is unaffected by this change.

Effect

On merge, the marketplace sync re-publishes the plugin and Desktop picks it up on next launch. Removed entries are pruned from the user's connector list automatically. No client release needed.

Follow-up

Restoring these entries would require a registered OAuth client suitable for local-loopback use plus a way to specify it in .mcp.json. That is tracked separately.

The Google-hosted MCP endpoints (gmail, calendar, drive) require an OAuth
client_id at connection time and do not support dynamic client registration.
The .mcp.json schema currently has no way to provide a client_id for these
endpoints, so the connection cannot succeed from this plugin.

This brings small-business in line with the other plugins in this repo, which
had the same entries removed in #184. Users can connect Gmail, Calendar, and
Drive through the Connectors Directory in the app, which handles the
authentication separately.
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