Excellent in goose, as one entry in its own config

The installer writes one excellent entry into ~/.config/goose/config.yaml, in YAML, under extensions, and leaves the rest of the file alone. Restart goose 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 goose: linked.

~/.config/goose/config.yaml

extensions:

excellent:

type: "stdio"

name: "Excellent"

enabled: true

cmd: "/absolute/path/to/node"

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

args:

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

env_keys: []

envs: {}

timeout: 300

Setup prompt · paste it into goose

Set up Excellent (excellent.so) in goose for me. First run: curl -fsSL https://excellent.so/install.sh | sh
If its output has a line starting "goose: linked" or "goose: already-linked", skip to the last step.
Otherwise add this to ~/.config/goose/config.yaml (create the file if it is missing). If the file already has a top-level extensions: map, put the excellent: entry inside it; keep everything else unchanged:
extensions:
  excellent:
    type: "stdio"
    name: "Excellent"
    enabled: true
    cmd: "/absolute/path/to/node"
    cwd: "/absolute/path/to/@excellent-so/cli/dist"
    args:
      - "/absolute/path/to/@excellent-so/cli/dist/server.js"
    env_keys: []
    envs: {}
    timeout: 300
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 goose, because it only sees the new server after a restart.

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

Agent: gooseAgentic AI Foundation
Config file: ~/.config/goose/config.yamlmacOS
Linux, Windows: Linux: the same path. Windows: %USERPROFILE%\AppData\Roaming\Block\goose\config\config.yamlNot supported yet
Format: YAML, under extensionsextensions, as a goose stdio extension
Detected by: the goose binary
The installer prints: goose: linked
Restart: Restart goose afterwards: it only sees the new server after a restart.
Undo: Delete the excellent: entry under extensions: in ~/.config/goose/config.yaml, then restart goose.
Source: micro packages/core/src/agent-clis.ts:948
goose 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.

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