Install GitHub Issue MCP in Goose

What you need first

• Goose, installed.
• Node.js, which gives the npx command the server starts with.
• Your own values for YOUR_GITHUB_TOKEN,YOUR_GITHUB_OWNER,YOUR_GITHUB_REPO,YOUR_GEMINI_API_KEY.

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:
  "github-issue-mcp":
    type: stdio
    name: "github-issue-mcp"
    enabled: true
    cmd: "npx"
    args: ["-y", "[email protected]"]
    env_keys: []
    envs: { "GITHUB_TOKEN": "YOUR_GITHUB_TOKEN", "GITHUB_OWNER": "YOUR_GITHUB_OWNER", "GITHUB_REPO": "YOUR_GITHUB_REPO", "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY" }
    timeout: 300

3. Replace YOUR_GITHUB_TOKEN,YOUR_GITHUB_OWNER,YOUR_GITHUB_REPO,YOUR_GEMINI_API_KEY with your own values.
4. Save the file and start a new Goose session.

Check it worked

Ask Goose: List the tools of github-issue-mcp.

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.

The server starts, but its tools fail

A YOUR_… placeholder is still in the config, or its value is wrong.

Nothing changes after a restart

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