geminicli-manage-addon

Geminicli Addon Manager is a text-based UI (TUI) tool designed to help you manage Geminicli extensions and MCP servers from within the terminal. It provides three core capabilities: managing extensions (enable/disable Geminicli extensions), managing MCP servers that live inside extensions, and managing standalone MCP servers defined in settings.json. The TUI presents a list of items and lets you navigate with the arrow keys, toggle enabled states with Space, and save changes with Enter. It also integrates with Geminicli via a slash command (/manage-addon) so you can launch the tool from Geminicli itself. When changes are saved, the addon automatically backs up configuration files, helping prevent data loss. The tool is built on Ink for a responsive terminal experience and emphasizes quick, lightweight management of complex configurations.

Prerequisites:

• Node.js >= 18.0.0
• Git (optional, for source installation)
• Geminicli installed and configured if you plan to integrate with Geminicli

Install from npm (recommended):

npm install -g geminicli-manage-addon

Install from source:

git clone https://github.com/castle-studio-work/geminicli-manage-addon.git
cd geminicli-manage-addon
npm install
npm link

Run locally (from any location where the CLI is available):

geminicli-manage-addon

If you installed from source and used npm link, ensure your environment PATH includes the global npm bin directory so the geminicli-manage-addon command is discoverable.

Tips and caveats:

• The tool automatically backs up configuration files before saving changes. If you encounter permission issues when saving, verify file permissions on the relevant JSON files under ~/.gemini (e.g., extension-enablement.json and settings.json).
• Ensure Node.js is at least v18.x to maximize compatibility with Ink-based UI and ES modules.
• When integrating with Geminicli, follow the in-tool instructions to restart Geminicli after making changes for them to take effect.
• If the CLI command cannot be found after installation, check your npm prefix and PATH: npm config get prefix and ensure $(npm config get prefix)/bin is in your PATH.
• This MCP server configuration focuses on orchestration and management of existing extension-based and standalone MCP servers; the addon itself is not a separate MCP server but a management tool.