goose-with s

This MCP server integrates a GitHub-based MCP provider into Goose, enabling you to add and manage a GitHub extension for the Goose environment. The server is run via NPX to install and execute the Model Context Protocol GitHub provider, which then configures Goose to connect to GitHub for MCP-based interactions. After starting, use Goose's configure flow to add the extension and provide the required environment variable, notably a GitHub Personal Access Token, so Goose can access GitHub resources on your behalf. The result is an extension named GitHub within Goose that can be used to route MCP commands to GitHub-backed workflows or data sources as defined by the provider.

Prerequisites:

• Node.js and npm (or pnpm) installed on your machine or in your development container
• Goose installed in your Devcontainer as described in the Goose setup instructions

Installation steps:

1. Ensure you have a GitHub Personal Access Token (PAT) with the scopes required by the GitHub MCP provider.

2. Open a terminal where Goose is configured.

3. Run the MCP server via NPX to install and execute the GitHub provider:

   npx -y @modelcontextprotocol/server-github

4. When prompted (as part of the Goose configure flow), provide the GitHub PAT when asked for the environment variable value for GITHUB_PERSONAL_ACCESS_TOKEN. This enables Goose to access GitHub resources for the MCP extension.

5. Complete the Goose extension configuration by following the prompts to name the extension (e.g., GitHub) and confirm the addition.

Notes:

• The configuration step stores the GitHub access token in Goose's config; ensure you protect this token appropriately.
• You can re-run goose configure later to adjust the settings or update the extension.

Tips and caveats:

• Ensure the PAT has the minimum required scopes for the GitHub actions you plan to trigger or read from via MCP.
• If running inside Docker/Devcontainer, use host.docker.internal (or equivalent) for any necessary local host references when configuring providers.
• Keep Goose and MCP provider versions in sync with your desired MCP features; check for updates to @modelcontextprotocol/server-github periodically.
• If you encounter network or authentication issues, re-check the PAT scope and ensure it is not expired or revoked.
• The mcp_config structure uses the server name server-github; you can rename it in your Goose config as needed, but keep the command and args aligned with the provider package.