hubspot: make CLIENT_ID and CLIENT_SECRET optional (1.0.1) - #454
Merged
minupalaniappan merged 1 commit intoSep 29, 2026
Merged
Conversation
Cursor is rolling out Grok's HubSpot MCP OAuth app behind a gate. With the fields optional, users it applies to can leave them blank, and everyone else can still bring their own client.
minupalaniappan
approved these changes
Sep 29, 2026
ericgyl817
approved these changes
Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Makes HubSpot CLIENT_ID and CLIENT_SECRET optional (1.0.1) so gated users can leave them blank and use Grok's HubSpot app. Everyone else can still set their own client. mcp.json is unchanged.
Note
Low Risk
Manifest and documentation only; no MCP wiring changes, with optional BYO OAuth still supported.
Overview
Bumps the HubSpot plugin to 1.0.1 and changes install so HubSpot Client ID and Client Secret are no longer required in
plugin.json(requiredis now empty).Variable descriptions and README / CHANGELOG explain that users can leave credentials blank to use Grok's HubSpot app where Cursor offers it, and only create their own MCP auth app when OAuth is not configured.
mcp.jsonis unchanged — it still passes${CLIENT_ID}and${CLIENT_SECRET}through MCP auth; the behavioral shift is at the plugin schema and docs layer.Reviewed by Cursor Bugbot for commit fba2ded. Bugbot is set up for automated code reviews on this repo. Configure here.