chore: update Gemini CLI extension name and description #208
Conversation
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
Updated the documentation to reflect the correct name of the extension and fixed minor formatting issues.
|
@benofben to kindly review 😄 |
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.
Gemini CLI team member here 👋
Gemini CLI extensions can be much more than just MCP servers, for that reason we highly recommend removing mcp from their names and instead just use the product (aka neo4j).
That way users leveraging the extension don't actually need to even know what MCP is 😄
Also the
descriptionfield in thegemini-extension.jsonpopulates the tile card for the extension in our gallery: https://geminicli.com/extensions/Current
New