Copilot: Not sending user-agent on MCP Oauth register
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
For some MCP services, when connecting a custom MCP server with OAuth, the DCR flow begins but fails at /register because Github Copilot does not send a User-Agent header. It is common to have protective rules requiring headers such as User-Agent on a request.
Example case where /register is denied due to missing User-Agent:
| Field | Value |
|---|---|
| App version | 1.1.19 |
| OS | macOS 26.6.2 |
| Theme | GitHub |
| Path | / |
| Tenure | Day 3 (Week 1) |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the OAuth DCR flow against a custom MCP server and inspect the request sent to /register. Confirm the request headers, then verify that the registration succeeds when the required User-Agent header is present.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100