Install @0x1f320.sh/why-did-you-render-mcp in Goose

What you need first

• Goose, installed.
• Node.js, which gives the npx command the server starts with.

Steps

1. Open ~/.config/goose/config.yaml. On Windows it is %APPDATA%\Block\goose\config\config.yaml.
2. Add this entry. If the file already has extensions, add only the entry inside it.

extensions:
  "why-did-you-render-mcp-server":
    type: stdio
    name: "why-did-you-render-mcp-server"
    enabled: true
    cmd: "npx"
    args: ["-y", "@0x1f320.sh/why-did-you-render-mcp"]
    env_keys: []
    envs: {}
    timeout: 300

3. Save the file and start a new Goose session.

Check it worked

Ask Goose: List the tools of why-did-you-render-mcp-server.

If it does not start

spawn npx ENOENT

Node.js is not on the PATH that Goose sees. Install it, or write the full path of npx in the config.

Nothing changes after a restart

The file is not valid YAML any more. Check that the entry is indented like the lines around it.