Excellent in Gemini CLI, as one entry in its own config

The installer writes one excellent entry into ~/.gemini/settings.json, in JSON, under mcpServers, and leaves the rest of the file alone. Restart Gemini CLI afterwards: it only sees the new server after a restart.

curl -fsSL https://excellent.so/install.sh | sh

It runs excellent install-agent-mcps, which writes the entry and prints Gemini CLI: linked.

~/.gemini/settings.json

{

"mcpServers": {

"excellent": {

"type": "stdio",

"command": "/absolute/path/to/node",

"args": [

"/absolute/path/to/@excellent-so/cli/dist/server.js"

"cwd": "/absolute/path/to/@excellent-so/cli/dist",

"env": {}

}

Setup prompt · paste it into Gemini CLI

Set up Excellent (excellent.so) in Gemini CLI for me. First run: curl -fsSL https://excellent.so/install.sh | sh
If its output has a line starting "Gemini CLI: linked" or "Gemini CLI: already-linked", skip to the last step.
Otherwise open ~/.gemini/settings.json (create it as {} if it is missing) and add this under the top-level "mcpServers" object, creating that object if needed and keeping everything else in the file unchanged:
"excellent": {"type":"stdio","command":"/absolute/path/to/node","args":["/absolute/path/to/@excellent-so/cli/dist/server.js"],"cwd":"/absolute/path/to/@excellent-so/cli/dist","env":{}}
Replace /absolute/path/to/node with the output of `node -p process.execPath`, and /absolute/path/to/@excellent-so/cli/dist with the output of `echo "$(npm root -g)/@excellent-so/cli/dist"`.
Last step: tell me to restart Gemini CLI, because it only sees the new server after a restart.

It runs the installer and looks for Gemini CLI: linked; if that line is missing it adds the entry by hand, then asks you to restart.

Agent: Gemini CLIGoogle
Config file: ~/.gemini/settings.jsonmacOS
Linux, Windows: Linux: the same path. Windows: %USERPROFILE%\.gemini\settings.jsonNot supported yet
Format: JSON, under mcpServersmcpServers, with type: "stdio"
Detected by: the gemini binary
The installer prints: Gemini CLI: linked
Restart: Restart Gemini CLI afterwards: it only sees the new server after a restart.
Undo: Delete the "excellent" entry under "mcpServers" in ~/.gemini/settings.json, then restart Gemini CLI.
Source: micro packages/core/src/agent-clis.ts:602
Gemini CLI docs

The CLI on npm today, 0.1.0 (checked October 23, 2026), predates install-agent-mcps: the installer skips this step, says so, and changes no agent config. Paste the setup prompt, or add the entry by hand as the setup doc shows.

The same entry

Put Excellent in your agent: install it, restart the agent, run one task

curl -fsSL https://excellent.so/install.sh | sh

Names and marks belong to their owners. Shown to say Excellent works with these agents, with no endorsement implied.

The entry and the setup prompt