GitHub Extension
🎥Plug & Play
Watch the demo
This tutorial covers how to add the GitHub MCP Server as a Goose extension to enable file operations, repository management, search functionality, and more.
TLDR
- Goose Desktop
- Goose CLI
Use Add custom extension
in Settings → Extensions to add a Streamable HTTP
extension type with:
Use goose configure
to add a Remote Extension (Streaming HTTP)
extension type with:
Endpoint URL
https://api.githubcopilot.com/mcp/
Custom Request Header
Authorization: Bearer <YOUR_GITHUB_PERSONAL_ACCESS_TOKEN>
Configuration
These steps configure the Remote MCP Server. For other deployment options, see the official GitHub MCP Server documentation.
- Goose Desktop
- Goose CLI
- Obtain a GitHub Personal Access Token
- Click the button in the top-left to open the sidebar
- Click
Extensions
- Click
Add custom extension
- On the
Add custom extension
modal, enter the following:- Extension Name: GitHub
- Type: Streamable HTTP
- Endpoint:
https://api.githubcopilot.com/mcp/
- Request Headers:
- Header name:
Authorization
- Value:
Bearer <YOUR_GITHUB_PERSONAL_ACCESS_TOKEN>
- Header name:
- Click
+ Add
to save the header - Click
Add Extension
to save the extension - Navigate to the chat
- Run the
configure
command:
goose configure
- Choose to add a
Remote Extension (Streaming HTTP)
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◆ What type of extension would you like to add?
│ ○ Built-in Extension
│ ○ Command-line Extension
│ ○ Remote Extension (SSE)
│ ● Remote Extension (Streaming HTTP) (Connect to a remote extension via MCP Streaming HTTP)
└
- Give your extension a name
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streaming HTTP)
│
◆ What would you like to call this extension?
│ github
└
- Enter the endpoint URI
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streaming HTTP)
│
◇ What would you like to call this extension?
│ github
│
◆ What is the Streaming HTTP endpoint URI?
│ https://api.githubcopilot.com/mcp/
└
- Enter the number of seconds Goose should wait for actions to complete before timing out. Default is
300
seconds
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streaming HTTP)
│
◇ What would you like to call this extension?
│ github
│
◇ What is the Streaming HTTP endpoint URI?
│ https://api.githubcopilot.com/mcp/
│
◆ Please set the timeout for this tool (in secs):
│ 300
└
- Choose to add a description. If you select
Yes
, you'll be prompted to enter a description for the extension
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streaming HTTP)
│
◇ What would you like to call this extension?
│ github
│
◇ What is the Streaming HTTP endpoint URI?
│ https://api.githubcopilot.com/mcp/
│
◇ Please set the timeout for this tool (in secs):
│ 300
│
◆ Would you like to add a description?
│ No
└
- Choose Yes when asked to add custom headers
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streaming HTTP)
│
◇ What would you like to call this extension?
│ github
│
◇ What is the Streaming HTTP endpoint URI?
│ https://api.githubcopilot.com/mcp/
│
◇ Please set the timeout for this tool (in secs):
│ 300
│
◇ Would you like to add a description?
│ No
│
◆ Would you like to add custom headers?
│ Yes
└
- Add your custom header
info
Obtain your GitHub Personal Access Token and paste it in
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streaming HTTP)
│
◇ What would you like to call this extension?
│ github
│
◇ What is the Streaming HTTP endpoint URI?
│ https://api.githubcopilot.com/mcp/
│
◇ Please set the timeout for this tool (in secs):
│ 300
│
◇ Would you like to add a description?
│ No
│
◇ Would you like to add custom headers?
│ Yes
│
◇ Header name:
│ Authorization
│
◇ Header value:
│ Bearer ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
│
◇ Add another header?
│ No
└ Added github extension
Example Usage
When creating my GitHub Personal Access Token, I gave it the following access:
- Repository: goose-demo
- Read access to metadata
- Read and Write access to code, commit status, issues, and pull requests
Goose Prompt
create a new branch called hello-world in my angiejones/goose-demo repository. Update the README.md file to say "this was written by goose" and commit it. Open a pull request with your changes.
Goose Output
I'll help you create a new branch, update the README, and open a pull request. Let me break this down into steps:
1. First, let's create the new branch called "hello-world" in your repository
2. Then update the README.md file
3. Finally, create a pull request
Let me execute these steps:
1. Creating the new branch:
─── create_branch | github ──────────────────────────
branch: hello-world
owner: angiejones
repo: goose-demo
2. Now, updating the README.md file in the new branch:
─── create_or_update_file | github ──────────────────────────
branch: hello-world
content: this was written by goose
message: Update README.md with Goose message
owner: angiejones
path: README.md
repo: goose-demo
3. Finally, creating the pull request:
─── create_pull_request | github ──────────────────────────
base: main
body: ...
head: hello-world
owner: angiejones
repo: goose-demo
title: Update README.md
Great! I've completed all the requested tasks:
1. Created a new branch called "hello-world"
2. Updated the README.md file with the text "this was written by goose"
3. Created a pull request to merge these changes into the main branch
You can view the pull request at: https://github.com/angiejones/goose-demo/pull/1
The pull request is now ready for your review. Would you like me to do anything else with it?