GitHub
GitHub hosts its MCP server at https://api.githubcopilot.com/mcp/. It does not register OAuth clients for you. The Official card defaults to an API key, which is a personal access token sent as a bearer. OAuth is also available if an admin creates a GitHub OAuth App or GitHub App and pastes its client ID and secret into Willow. It is the GitHub card with the Official badge. Willow also has a built-in GitHub connector.
GitHub Apps issue short-lived tokens with fine-grained permissions, and must be installed on the organization. OAuth Apps are simpler and do not need an install.
API key
- In GitHub, open Settings → Developer settings → Personal access tokens and create a token with the access the agent needs.
- In Willow, add the Official GitHub card and keep API key.
- Paste the token. Willow sends it as a bearer token.
- Assign groups and Publish.
Everyone who uses this server shares that token's access.
OAuth
Use this when each person should sign in as themselves.
- In GitHub, go to Settings → Developer settings → OAuth Apps → New OAuth App (or create a GitHub App).
- Set Authorization callback URL to the redirect URI from Willow's setup step.
- Copy the Client ID and generate a Client Secret.
- In Willow, switch the Official card to OAuth sign-in and paste both.
- If the organization restricts third-party OAuth apps, an owner must approve the app under Organization settings → Third-party Access.
- Each person clicks Check connection and approves the app.
Troubleshooting
Sign-in succeeds for you and fails for everyone else
Cause: The OAuth App is owned by an organization that requires owner approval.
Solution: An organization owner approves the app before other members can authorize it.