Add GitHub MCP Server via Github app
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 24.6k
- Avg merge
- 22h 9m
- Merged PRs (30d)
- 610
Description
### Self Checks
- [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542).
- [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general).
- [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones.
- [x] I confirm that I am using English to submit this report, otherwise it will be closed.
- [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
- [x] Please do not modify this template :) and fill in all the required fields.
### Dify version
1.14.2
### Cloud or Self Hosted
Self Hosted (Docker)
### Steps to reproduce
1. Add an MCP server pointing to `https://api.githubcopilot.com/mcp/`
2. Add Github OAuth app 's client id and secret
2. Trigger the OAuth authorization flow (no static Authorization header).
3. Authorization fails
### ✔️ Expected Behavior
MCP server could be authenticated with a GH app, not just by adding a PAT via header (as #22808)
### ❌ Actual Behavior
```
ERROR [auth_client.py:122] Authentication retry failed
Traceback (most recent call last):
raise MCPAuthError(response=response_or_error.response)
core.mcp.error.MCPAuthError: Authentication failed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
raise ValueError(
ValueError: Client credentials token request failed: HTTP 404, Response: Not Found
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/api/core/mcp/auth_client.py", line 94, in _handle_auth_error
raise ValueError(f"Client credentials flow failed: {e}")
ValueError: Client credentials flow failed: Client credentials token request failed: HTTP 404, Response: Not Found
```
Contributor guide
Assessment
This issue has not been assessed yet.