Excellent in Grok Build, as one entry in its own config

The installer writes one excellent entry into ~/.grok/config.toml, in TOML, under [mcp_servers.excellent], and leaves the rest of the file alone. Restart Grok Build 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 Grok Build: linked.

~/.grok/config.toml

[mcp_servers.excellent]

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 Grok Build

Set up Excellent (excellent.so) in Grok Build for me. First run: curl -fsSL https://excellent.so/install.sh | sh
If its output has a line starting "Grok Build: linked" or "Grok Build: already-linked", skip to the last step.
Otherwise add this block to ~/.grok/config.toml (create the file if it is missing; if it already has an [mcp_servers.excellent] block, replace only that block):
[mcp_servers.excellent]
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 Grok Build, because it only sees the new server after a restart.

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

Agent: Grok BuildxAI
Config file: ~/.grok/config.tomlmacOS
Linux, Windows: Linux: the same path. Windows: %USERPROFILE%\.grok\config.tomlNot supported yet
Format: TOML, under [mcp_servers.excellent]a [mcp_servers.excellent] table
Detected by: the grok binary
The installer prints: Grok Build: linked
Restart: Restart Grok Build afterwards: it only sees the new server after a restart.
Undo: Delete the [mcp_servers.excellent] block from ~/.grok/config.toml, then restart Grok Build.
Source: micro packages/core/src/agent-clis.ts:640
Grok Build 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