Align the registry description with the npm one - #46
Merged
Conversation
The MCP registry line said less than the npm description: it dropped the keyword + semantic pairing, the relevance-ranked SQL aggregation, the plain-files index, and the no-accounts/no-keys/no-server close. One line, now identical in substance on both surfaces.
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
1 participant
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.
One line. The MCP registry description lagged the npm one and said less about what makes the tool worth picking.
Before: "Local code search for AI coding agents: hybrid search and SQL aggregation over an in-repo index."
After: "Local code search for AI coding agents: hybrid keyword + semantic search and SQL relevance-ranked aggregation over an index that lives in plain files. No accounts, no keys, no server."
README, keywords, plugin manifests, and tool descriptions are already in this shape and stay untouched. The registry and the aggregators re-pull the description on the next npm publish.