Atlassian MCP auth fails in Copilot Desktop with:
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Atlassian MCP auth fails in Copilot Desktop with:
`Incompatible authorization server: authorization server advertised an issuer that does not match the URL its metadata was discovered from (RFC 8414 §3.3)`
Exact error after clicking on sign-in: "Authentication failed
Atlassian: RPC error -32603: Request session.mcp.oauth.login failed with message: Incompatible authorization server: authorization server advertised an issuer that does not match the URL its metadata was discovered from (RFC 8414 §3.3); refusing to connect"
Endpoint: `https://mcp.atlassian.com/v1/mcp`
Worked previously; started after re-auth prompt.
Repro: Add MCP server → click Sign in → fails immediately.
---
| Field | Value |
| --- | --- |
| App version | 1.1.9 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 5 (Week 1) |
Contributor guide
Research direction
Start by reproducing the sign-in failure for https://mcp.atlassian.com/v1/mcp in Copilot Desktop on the reported Windows setup, then trace the MCP OAuth login path and its RFC 8414 metadata handling. Done means the Atlassian MCP server can be added and sign-in completes without the issuer-mismatch error.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100