Still report error : Authorization error, you may need to run /login
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
### Describe the bug
✗ Authorization error, you may need to run /login (Request ID:
D563:31F14:D195DE:F343F3:69DDC5C8)
! Failed to connect to MCP server 'github-mcp-server'. Execute '/mcp show
github-mcp-server' to inspect or check the logs.
● GitHub MCP Server: Connected
● Signed in successfully as BH1SCW!
! Failed to connect to MCP server 'github-mcp-server'. Execute '/mcp show
github-mcp-server' to inspect or check the logs.
● MCP Servers reloaded: 0 servers connected
✗ Authorization error, you may need to run /login (Request ID:
D563:31F14:D2D435:F4B472:69DDC627)
### Affected version
1.0.22- 1.0.25
### Steps to reproduce the behavior
why I have login but still can't use it
### Expected behavior
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by reproducing the failure on versions 1.0.22–1.0.25, then run `/mcp show github-mcp-server` and inspect the logs as the report suggests. Compare the successful `/login` and MCP reload messages with the authorization errors; done means identifying why the connected GitHub MCP server still rejects requests and documenting or fixing the authentication path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100