This ticket proposes updating the names of the Neo.mjs-related MCP servers within .gemini/settings.json to include "neo.mjs" for improved branding and clarity.
Motivation:
Currently, the MCP servers are named neo-github-workflow, neo-knowledge-base, and neo-memory-core. By prefixing them with "neo.mjs", their association with the Neo.mjs framework becomes immediately clear, enhancing branding and consistency across the ecosystem. This is a low-effort change with a positive impact on identification.
Changes Proposed:
Update the mcpServers configuration in .gemini/settings.json as follows:
neo-github-workflow -> neo.mjs-github-workflowneo-knowledge-base -> neo.mjs-knowledge-baseneo-memory-core -> neo.mjs-memory-core
This change will be purely cosmetic at this stage, affecting only the display name within the Gemini CLI. Future steps would involve updating the internal server names and package.json files when these servers are externalized.
This ticket proposes updating the names of the Neo.mjs-related MCP servers within
.gemini/settings.jsonto include "neo.mjs" for improved branding and clarity.Motivation: Currently, the MCP servers are named
neo-github-workflow,neo-knowledge-base, andneo-memory-core. By prefixing them with "neo.mjs", their association with the Neo.mjs framework becomes immediately clear, enhancing branding and consistency across the ecosystem. This is a low-effort change with a positive impact on identification.Changes Proposed: Update the
mcpServersconfiguration in.gemini/settings.jsonas follows:neo-github-workflow->neo.mjs-github-workflowneo-knowledge-base->neo.mjs-knowledge-baseneo-memory-core->neo.mjs-memory-coreThis change will be purely cosmetic at this stage, affecting only the display name within the Gemini CLI. Future steps would involve updating the internal server names and
package.jsonfiles when these servers are externalized.