Skip to content

SCR-395: move the Cursor plugin to its own folder - #38

Merged
sahilsunny merged 1 commit into
mainfrom
sahil/scr-395-cursor-plugin-folder
Oct 13, 2026
Merged

sahilsunny merged 1 commit into
mainfrom
sahil/scr-395-cursor-plugin-folder

Conversation

@sahilsunny

Copy link
Copy Markdown
Collaborator

What

  • Moves the Cursor manifest, mcp.json and logo from plugins/scrapingbee-cli/ to a new plugins/scrapingbee-cursor/ folder, with its own README, LICENSE and a synced copy of the skills (sync-skills.sh has it as a fifth target).
  • Adds a root .cursor-plugin/marketplace.json pointing at that folder.
  • Adds the directory listing fields (icon, documentationUrl, supportUrl, privacyPolicyUrl, termsOfServiceUrl) to the Claude plugin manifest.

Why

The Claude plugin directory's scanner read mcp.json (the Cursor config with Authorization: Bearer ${SCRAPINGBEE_API_KEY}) and put the submission on a reviewer hold for "uses a credential from the user's machine" — a hold that would repeat on every version. With the Cursor files in their own folder, the Claude folder contains only manifests and skills, so it validates clean. The listing fields are what the directory reads for the icon and links.

Verification

claude plugin validate passes for the Claude folder; the Cursor CLI loads the new folder with both skills and the MCP server (18 tools); check_examples.py passes; all skill copies are identical to .agents/skills/.

…ory listing fields

The Claude plugin folder keeps only the Claude and Codex manifests, so directory
scanners no longer find an MCP config with a credential variable beside the skills.
plugins/scrapingbee-cursor/ holds the Cursor manifest, mcp.json, logo and a synced
copy of the skills; a root .cursor-plugin/marketplace.json points at it.
@sahilsunny
sahilsunny requested a review from a team October 13, 2026 11:21
@sahilsunny
sahilsunny merged commit e257eae into main Oct 13, 2026
14 checks passed
@sahilsunny
sahilsunny deleted the sahil/scr-395-cursor-plugin-folder branch October 13, 2026 13:40
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.

2 participants