Locally running MCP servers 127.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Locally running MCP servers 127.0.0.1 unregistered from the session during the recent github rest api outage. I had to build a bridge. May not make sense to disconnect local like this if it is possible. e.g. Options -> MCP Servers -> MyLocalMCPTool just sat and spun trying to load when it was fully available.
---
| Field | Value |
| --- | --- |
| App version | 1.0.24 |
| OS | Windows 10.0.26100 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 4 |
Contributor guide
Research direction
Start in the /chat flow and reproduce the issue through Options → MCP Servers with a locally running 127.0.0.1 server while the GitHub REST API is unavailable. Done means the local MCP server remains registered in the session and loads instead of spinning indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100