-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Problem
When setting up the GitHub MCP Server, the README doesn't clearly mention that you need to be authenticated against GitHub Copilot. This causes confusion during setup because:
- The remote server URL () hints at the Copilot requirement, but it's not explicitly documented
- Users may encounter authentication errors without understanding why
- The setup process requires trial and error to figure out the authentication dependency
Expected behavior
The README should clearly document:
- That GitHub Copilot authentication/subscription is required for the remote server
- How to authenticate with GitHub Copilot if needed
- Any prerequisites related to Copilot access
Current behavior
Users have to figure out the Copilot authentication requirement through trial and error by:
- Noticing the domain in the configuration
- Encountering authentication failures
- Deducing the requirement from error messages
Suggested solution
Add a clear note in the Prerequisites section mentioning the GitHub Copilot authentication requirement for the remote server option.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
docs: Add GitHub Copilot authentication requirement to README
matthewp commentedon Jun 25, 2025
Thank you for this, I've been pounding my head wondering why a GH App gets a 403 response.
Are there instructions on how to do this?