MCP OAuth: 'needs authentication' link never launches any visible auth flow (Atlassian/Jira, macOS, CLI 1.0.83)
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 45/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 領域
- api, authentication, cli
研究方向
在啟用 https://mcp.atlassian.com/v1/mcp 的情況下，重現 Copilot 應用程式 agents 視窗中的流程，然後將其與 ~/.copilot/mcp-config.json、copilot mcp list 和 ~/.copilot/mcp-oauth-config/ 所描述的獨立 CLI 狀態進行比較。追蹤驗證連結的交接流程和瀏覽器啟動入口；完成條件是連結能開啟系統瀏覽器或顯示可複製的原始 URL，並且 Atlassian 工具在 callback 後變得可用。
由索引模型根據 Issue 內容生成。
描述
Describe the bug
The Atlassian (Rovo) MCP server repeatedly shows a "Jira MCP needs authentication" prompt, but clicking the provided authentication link — or attempting to authenticate manually — never launches any visible auth flow. No browser window/tab opens, no OAuth consent page appears, and nothing surfaces in the UI. The prompt simply reappears, so the server can never be authenticated and its tools are never usable.
This is the browser-launch / auth-hand-off side of MCP OAuth, not the token-bridging bug in #4096 (which is fixed on my version). It looks related to #4400 (browser login URL wrapping/fallback) and #3130 (unable to open browser for auth).
Affected version
GitHub Copilot CLI 1.0.83 (bundled engine used by the Copilot desktop app "agents" window).
Environment
- macOS (Apple Silicon)
- The failing flow is in the app / agents window, which manages its own MCP configuration.
- The standalone terminal CLI has no MCP servers configured (
~/.copilot/mcp-config.json={"mcpServers":{}},copilot mcp list= "No MCP servers configured", and~/.copilot/mcp-oauth-config/does not exist). So the Atlassian server exists only on the app side, and it is the app-side "authenticate" link that dead-ends.
Steps to reproduce the behavior
- In the Copilot app (agents window), add/enable the Atlassian Remote MCP server (
https://mcp.atlassian.com/v1/mcp). - When prompted with "Jira MCP needs authentication", click the provided authentication link (or choose to authenticate manually).
- Observe: no browser opens, no OAuth consent page appears, nothing visible happens.
- The "needs authentication" prompt returns; the server never becomes authenticated and no
atlassian-*tools are exposed.
Expected behavior
Clicking the authentication link should open the system default browser to the OAuth consent URL (or, if the browser cannot be launched, print/copy the raw URL so it can be opened manually) and complete the callback so the server authenticates.
Additional notes
- This consistently blocks my workflow — the Atlassian/Jira MCP tools are never available because auth can never be completed.
- A raw-URL fallback (print the login URL to stdout / provide a copyable link) would at minimum unblock manual authentication when auto-launch fails.
- 主要語言
- Shell
- 星號
- 11.2k
- 分支
- 1.9k
- 平均合併
- 17 小時 6 分鐘
- 30 天內合併 PR
- 5
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/copilot-cli 的其他 Issue
-
area:sessions
難度 2/5 1-3 小時 新手友好度 72/100
github/copilot-cli#4996 ·
維護者通常 1 天內回覆
-
triage
難度 1/5 1 小時以內 新手友好度 88/100
github/copilot-cli#4963 · 1 則留言 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 75/100
github/copilot-cli#4932 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 78/100
github/copilot-cli#4909 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 76/100
github/copilot-cli#4906 ·
維護者通常 1 天內回覆
查看 github/copilot-cli 的全部 Issue
相似的 Issue
-
documentation
難度 1/5 1 小時以內 新手友好度 90/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 92/100
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
obra/superpowers#2445 ·
維護者通常 5 天內回覆
-
package-update
難度 2/5 1-3 小時 新手友好度 78/100
oSoWoSo/vOid_Community_repOsitory#240 · 1 則留言 ·
維護者通常 1 天內回覆
-
ai-inspected
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆