feat(cursor): add the marketplace plugin manifest - #1
Merged
Conversation
MAR-255 listed cloro on cursor.directory, the community index. The official
Cursor marketplace needs a public repo carrying a plugin manifest, which did
not exist when that ticket closed. MAR-295 made this repo public, so it does.
Cursor holds the key and sends it as Authorization: Bearer, so the plugin
avoids the path-embedded form. No key ships in the repo.
Tested against mcp.cloro.dev with header auth: initialize returns
serverInfo 0.1.0 and tools/list returns all 10 tools, each with
readOnlyHint true.
The test guards the checklist items that cost a review round trip: the
version now lives in a fourth file, the logo must be committed and
relative, and every ${VAR} in mcp.json must be declared in the manifest
variables or the server 401s for every user who installs the plugin.
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
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.
What
Makes this repo submittable to the official Cursor marketplace at
cursor.com/marketplace/publish..cursor-plugin/plugin.json— manifest, declaresCLORO_API_KEYas the one required variablemcp.json— points athttps://mcp.cloro.dev/mcpwithAuthorization: Bearer ${CLORO_API_KEY}assets/logo.svg— the square icon mark, committed and referenced by relative path as the checklist requiressrc/cursor-plugin.test.ts— 6 guardsWhy
MAR-255 listed cloro on cursor.directory, which is the community index. The official marketplace is a separate submit-and-review surface and needs a public repo carrying a plugin manifest. No public repo existed when MAR-255 closed, which is why it was never attempted; MAR-295 made this repo public.
Cursor stores the key its side and sends it as a header, so this listing avoids the path-embedded key form that MAR-255 records as the recurring friction point.
Tested
Against the live
mcp.cloro.devwith header auth, which is the exact config inmcp.json:initializereturnsserverInfocloro0.1.0tools/listreturns all 10 tools, each withreadOnlyHint: truenpx vitest run40/40 pass,tsc --noEmitclean.On the test
Three checklist items cost a review round trip rather than a test failure, so they are guarded:
package.json,server.jsonandsrc/server.ts..and no leading/${VAR}inmcp.jsonmust be declared in the manifestvariablesand marked required. This is the one failure with no local symptom: an undeclared placeholder is never prompted for, so the server 401s for every user who installs the plugin.