Repository navigation
[Issue] Github MCP connector: 415 error #132
Description
Issue Description
Github MCP connector suddenly started giving 415 error. It was working till now.
It is a PAT based connector
Thread ID
N.A
Steps to Reproduce
- Go to SRE agent.
- Go to connector
- Add connector.
- Click on MCP connectors.
- Github connector, provide URL and valid PAT token.
Expected Behavior
Github connector should work with test connection returning all tools.
Actual Behavior
It is giving 415 error
Activity
dm-chelupati commentedon Apr 19, 2026
Thanks for reporting this. This is a confirmed bug on our side, not a configuration issue.
A recent change in GitHub's MCP server introduced stricter Content-Type validation that is incompatible with how our SDK sends HTTP requests. We have a fix in progress and will update this issue once it's deployed.
dm-chelupati commentedon Apr 27, 2026
This issue has been resolved. The root cause was twofold:
GitHub's MCP server (Go SDK) introduced strict Content-Type validation that rejected requests with application/json; charset=utf-8 (the default sent by .NET's HttpClient). GitHub has fixed this on their side by upgrading to Go SDK v1.5.0 with proper media type parsing (github/github-mcp-server#2336).
SRE Agent also shipped a fix to use AutoDetect transport mode instead of hardcoding StreamableHttp, improving compatibility with MCP servers that have varying transport support.
Both fixes are now deployed. GitHub MCP connectors with PAT-based authentication are working as expected. Please reopen if you encounter further issues.