Connect Goose to Niro
One command connects Goose to Niro:
niro mcp install --client goose
Then restart Goose, because it reads its settings only when it starts.
You must have run niro start first, so that you are signed in. See Connect your coding agent to Niro.
What the install writes
- An
extensions.niroentry (type stdio, timeout 300 seconds) in~/.config/goose/config.yaml. On Windows the file is%APPDATA%\Block\goose\config\config.yaml.
How Goose learns to use Niro
- Nothing beyond the connection.
Check that it works
Ask it a question about your code, such as "which routes does this project serve?". An answer from Niro starts with "Answered from the local graph on this machine (niro-local)."
Things to know
- If your Goose settings file is laid out in a way the installer does not expect, it does not change it. It prints the block for you to paste instead.
Remove it
niro mcp uninstall --client goose
If something goes wrong, see FAQ: coding agents and MCP.