[BUG] Cowork GitHub connector shows Connected but exposes no MCP tools — OAuth token missing user:mcp_servers scope (regression of #23775)

Preflight Checklist

• [x] I have searched existing issues and confirmed this is a regression of a previously-closed issue (#23775), not a duplicate of an open one
• [x] This is a single bug report
• [x] I am using the latest version of Claude Code

---

What's Wrong?

The GitHub Integration connector in Cowork shows as Connected in the UI after completing the OAuth flow. However, no GitHub MCP tools are available in the session. Inspecting the token reveals it was granted only user:inference scope — user:mcp_servers is never requested during the OAuth flow. The connection is functionally useless.

This is a regression of #23775 (closed as fixed 14 Feb 2026). Related open issues: #28695 (OAuth scope never requested), #26259 (tools unavailable after connect).

---

What Should Happen?

After connecting the GitHub Integration connector, Claude should have MCP tools available for GitHub operations — reading repos, listing issues, creating issues, etc.

---

Steps to Reproduce

1. Open Cowork desktop app
2. Settings → Connectors → GitHub Integration → Connect
3. Complete the OAuth flow
4. Start a new session
5. Ask Claude to access a GitHub repo or list issues
6. Claude reports no GitHub tools available

---

Error Messages/Logs

No error shown. Connector displays as Connected. Claude simply has no GitHub tools in scope.

---

Is this a regression?

Yes — this worked in a previous version. #23775 was closed as fixed on 14 Feb 2026 and has since regressed.

---

Last Working Version

Unknown — regression discovered in 2.1.68.

---

Claude Code Version

2.1.68 (Claude Code)

---

Platform

Anthropic API

---

Operating System

macOS

---

Terminal/Shell

N/A — Cowork desktop app

---

Additional Information

Workaround: use context-mode MCP to run gh CLI via shell on the local machine. The session disruption caused by this bug was significant — Claude incorrectly declared GitHub access impossible, then attempted headless browser workarounds invisible to the user, before the shell workaround was found.