Non-whitelisted MCP's keep connecting instead of showing error
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
### Short summary
Non-whitelisted MCP's keep connecting (showing spinner) instead of showing error
### Affected version or release
v1.0.23
### Installation context
_No response_
### What happened?
On an ghe.com with 'Restrict MCP access to registry servers' set to registry only when trying to use an non-whitelisted MCP server it keeps spinning/connecting instead of showing an error
### Steps to reproduce
1. Have 'Restrict MCP access to registry servers' set to registry only
2. Add non-whitelisted MCP server
3. MCP server keeps connecting/spinning
### Expected behavior
1. Have 'Restrict MCP access to registry servers' set to registry only
2. Add non-whitelisted MCP server
3. MCP server shows error / whitelisting error
### Additional context
_No response_
Contributor guide
Research direction
Start by reproducing the issue on ghe.com with “Restrict MCP access to registry servers” set to registry only, then add a non-whitelisted MCP server and observe the connection state. Trace the code responsible for MCP connection failures and verify that the server stops spinning and displays a whitelisting error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100