Skip to content

feat: tag the plugin's server URL with the cursor-plugin distribution channel#4

Open
lovable-odd wants to merge 1 commit into
mainfrom
odd/src-channel-tag
Open

feat: tag the plugin's server URL with the cursor-plugin distribution channel#4
lovable-odd wants to merge 1 commit into
mainfrom
odd/src-channel-tag

Conversation

@lovable-odd

@lovable-odd lovable-odd commented Jul 8, 2026

Copy link
Copy Markdown

Adds ?src=cursor-plugin to the bundled server URL in plugins/lovable/mcp.json so Lovable usage analytics can attribute traffic to the Cursor plugin channel (vs manual setup / other channels).

  • Privacy note: the tag identifies the distribution channel of this config file ("installed via the Cursor plugin"), not the user — it is a static string, identical for every install, and adds no data about you or your machine to what the server already receives.
  • The param is read by the Lovable MCP worker behind a strict allowlist (^[a-z0-9._-]{1,64}$) and recorded on the usage event; it changes nothing about the connection or OAuth flow and is inert to the MCP protocol.
  • The set of allowed tags is maintained in an internal registry (Lovable monorepo, workers/mcp-server/README.md) — cursor-plugin is this repo's designated entry.
  • Scoped to the plugin config only; README snippets stay untagged (= manual channel).
  • Internal context (links need Lovable access): mechanism PR lovablelabs/lovable#61404 · tracking ticket INS-785 (full attribution project + canonical tag registry rationale).

Verified in production (2026-07-08): a Claude Code client configured with ?src=test produced correctly-tagged analytics events end-to-end — the query param survives the full chain and the pipeline records it. This PR points the tag at its real channel value; Cursor-specific confirmation follows from the first tagged request after merge.

Per-channel verification happens on the Lovable side once this merges (first request with src=cursor-plugin in analytics).

🤖 Generated with Claude Code

… channel

Lovable usage analytics attribute requests to a distribution channel via
an allowlisted ?src= query param on the configured server URL (canonical
tag registry: workers/mcp-server/README.md in the monorepo). Clients echo
the configured URL on every request; the param is inert otherwise.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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