Excellent in GitLab Duo CLI, as one entry in its own config

The installer writes one excellent entry into ~/.gitlab/duo/mcp.json, in JSON, under mcpServers, and leaves the rest of the file alone. Restart GitLab Duo 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 GitLab Duo CLI: linked.

~/.gitlab/duo/mcp.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 GitLab Duo CLI

Set up Excellent (excellent.so) in GitLab Duo CLI for me. First run: curl -fsSL https://excellent.so/install.sh | sh
If its output has a line starting "GitLab Duo CLI: linked" or "GitLab Duo CLI: already-linked", skip to the last step.
Otherwise open ~/.gitlab/duo/mcp.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 GitLab Duo CLI, because it only sees the new server after a restart.

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

Agent: GitLab Duo CLIGitLab
Config file: ~/.gitlab/duo/mcp.jsonmacOS
Linux, Windows: Linux: the same path. Windows: %USERPROFILE%\AppData\Roaming\GitLab\duo\mcp.jsonNot supported yet
Format: JSON, under mcpServersmcpServers, with type: "stdio"
Detected by: the duo binary
The installer prints: GitLab Duo CLI: linked
Restart: Restart GitLab Duo CLI afterwards: it only sees the new server after a restart.
Undo: Delete the "excellent" entry under "mcpServers" in ~/.gitlab/duo/mcp.json, then restart GitLab Duo CLI.
Source: micro packages/core/src/agent-clis.ts:809
GitLab Duo 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