Skip to content

feat: drop pre-registered OAuth client ID now that DCR supports Cursor - #5

Open
alexisb24 wants to merge 1 commit into
mainfrom
alexisb24/dcr-drop-client-id
Open

feat: drop pre-registered OAuth client ID now that DCR supports Cursor#5
alexisb24 wants to merge 1 commit into
mainfrom
alexisb24/dcr-drop-client-id

Conversation

@alexisb24

Copy link
Copy Markdown
Collaborator

Summary

Lovable's OAuth server now supports dynamic client registration, and lovablelabs/lovable#87538 allowlists Cursor's two OAuth callbacks (cursor://anysphere.cursor-mcp/oauth/callback for the IDE, https://www.cursor.com/agents/mcp/oauth/callback for cloud agents / the CLI) in open DCR. With that live, Cursor connects with plain OAuth like any other client and the pre-registered CLIENT_ID workaround is no longer needed.

Changes:

  • plugins/lovable/mcp.json — drop the auth.CLIENT_ID block; the ?src=cursor-plugin channel tag stays.
  • plugins/lovable/README.md — same for the manual-setup snippet.
  • plugins/lovable/.cursor-plugin/plugin.json — version bump to 0.1.1.
  • plugins/lovable/CHANGELOG.md — 0.1.1 entry.

Merge gating

Do not merge or re-publish the marketplace listing until lovablelabs/lovable#87538 has merged and the OAuth server deploy is live — before that, DCR still rejects Cursor's redirect URIs and a client-id-less config fails to authenticate. After deploy, verify with a fresh Cursor install that adding the server without the auth block completes the browser OAuth flow.

Existing installs are unaffected either way: the legacy client id 6d465f583e1e4ce5801b1616f735670c stays registered and keeps working.

Lovable project: https://lovable.dev/projects/1e858a99-305e-41b0-b9d2-e8f1e6012c0b

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