Workaround
The config was passing the environment to docker but not into the container, so it needs to be passed into the container.
The error
Visit https://github.com/login/device and enter the code XXXX-XXXX to authorize the GitHub MCP Server.Reported in github/github-mcp-server issue #2812: “MCP asks RW grants for RO access”.
What fixed it
your config is slightly incorrect, and you are passing the env to docker but not to the container.
— a maintainer's comment on the issue.
Source and dates
| Repository | github/github-mcp-server |
|---|---|
| Issue | MCP asks RW grants for RO access |
| Evidence | a maintainer's comment |
| Status | Workaround (a way around it, given in the evidence) |
| Fixed in | No version is named |
| Issue closed | 2026-07-14 |
| Read from GitHub | 2026-11-07 |
| Approved by a person | 2026-11-07 |
This page records what the vendor's own GitHub repository says. The error text, the issue title and the quote are copied as written; the summary at the top is one sentence limited to the quote, and a person approved this fact on 2026-11-07. KanseiLink has not re-run the fix. Read the issue before applying it. Something changed? Write to contact@synapse-arrows.com.
For AI agents
The same fact is returned as issue_facts by lookup({ service_id: 'github' }) on the KanseiLink MCP server (https://mcp.kansei-link.com/mcp), next to the other checked facts for GitHub. Connection guide: GitHub service page.
Other GitHub MCP errors
- GitHub MCP: "Failed to start MCP client for remote server gh-copilot_spaces: Error: Error POSTing to…" — the fix from the official GitHub issue
- GitHub MCP: "OAuth flow doesn't just work with my agent (moo) for lack of OASM" — the fix from the official GitHub issue
- GitHub MCP: "POST https://api.github.com/repos/{owner}/{repo}/issues/{issue_number}/comments: 403 Must…" — fixed (see the issue)
- GitHub MCP lockdown mode (prompt injection defense, issue #844)
- GitHub MCP: "how can we enable using mcp server in github copilot for jet brains?" — the fix from the official GitHub issue
- GitHub MCP: "--read-only flag fails to restrict write tools when using the new http command" — the fix from the official GitHub issue
- GitHub MCP: "Github MCP Server Not Exposing Full Toolset (Missing Actions, Workflows, and Run Status…" — the fix from the official GitHub issue
- GitHub MCP: "The listed users and repositories cannot be searched either because the resources do not…" — the fix from the official GitHub issue
- GitHub MCP: "Incompatible auth server: does not support dynamic client registration" — the fix from the official GitHub issue
- GitHub MCP: "MCP error -32603: Not Found: Resource not found: Not Found" — the fix from the official GitHub issue
- GitHub MCP: "Invalid schema for function 'get_me': In context=(), object schema missing properties." — fixed in v0.24.1
- GitHub MCP: "Error sending message to https://api.githubcopilot.com/mcp/: TypeError: fetch failed" — the fix from the official GitHub issue
- GitHub MCP: "Tool 'get_me' not found" — the fix from the official GitHub issue
- GitHub MCP: "get_copilot_space and list_copilot_spaces are not appearing anymore in the github MCP…" — the fix from the official GitHub issue
- GitHub MCP: "docker: Error response from daemon: Head…" — the fix from the official GitHub issue