Repository navigation
Make this MCP server discoverable in more directories - #1
Merged
Merged
Conversation
The MCP server key is what people see in their Cursor and Gemini config, so use the product name rather than the SDK repo name. server.json is removed because QRFLOW is already in the Official MCP Registry as codes.qrflow/qrflow at 1.0.0. Adding it under a second name would create a duplicate entry, and Glama, PulseMCP and the awesome lists all copy from the registry. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
This adds 4 files that 4 MCP directories look for, so people can find and install QRFLOW.codes. Your code does not change.
.mcp.json(new).mcp.json(Claude Code, for example) offer this server to people who open the repo.glama.json(new)gemini-extension.json(new)gemini-cli-extensiontopic.server.json(new)Once that is out, ManyCP publishes your server to the registry and keeps it current on every sync.
Optional: publish to the registry from GitHub Actions
Save this as
.github/workflows/publish-mcp.yml. It is not part of this pull request: GitHub only lets a token with theworkflowpermission write that folder, and ManyCP does not ask for it. It only tells the registry about a version. Your own release pipeline still publishes the package.Opened with ManyCP (https://manycp.com) on behalf of @nativecodeapps, who has push access to this repo. Close it if you would rather do this by hand.