Repository navigation
MCP server unavailable is reported as "waiting on ide" and hangs copilot-cli #4552
Description
Describe the bug
If you have an entry like this in your ~/.copilot/mcp-config.json
"dummy": {
"tools": [
"*"
],
"type": "http",
"url": "http://bextop17:4000/mcp",
"headers": {
"Authorization": "Bearer token"
}
}
And the host is unavailable (it is in DNS but the system as a whole is unreachable) then copilot will hang on startup eventually showing the message "waiting on ide." IDE is not in use.
Important: using a non-existent dns name will NOT recreate this error. The host must be defined in DNS and not available. Using an existing host with a down service (system up, but port not) will NOT recreate this. My tests were confirmed by unplugging a system next to me's ethernet cable.
Affected version
GitHub Copilot CLI 1.0.81-6
Steps to reproduce the behavior
- Define an mcp server for a system that has a valid dns name but is not on the network
- start copilot cli
- see error
Expected behavior
The cli should report the correct error message and not hang on a missing mcp server.
Additional context
This is on MacOS 15.7.7 (24G720) connecting to an mcp server on my local network which I had unplugged from the network for $reasons. This left the name in DNS but the system unavailable.
Activity
[-]MCP server unavailable is reported as "waiting on ice" and hangs copilot-cli[/-][+]MCP server unavailable is reported as "waiting on ide" and hangs copilot-cli[/+]xalvarez commentedon Sep 15, 2026
I believe I am encountering the same issue with a VPN-only MCP server.
I have an HTTP MCP server configured that is accessible only while connected to my company's VPN. When I start Copilot CLI while disconnected from the VPN, the MCP server cannot be reached and the CLI becomes effectively unusable.
In particular, I cannot switch to another custom agent after the MCP connection failure. I also have custom skills configured. Connecting to the VPN and restarting Copilot CLI restores normal operation.
This seems equivalent to the reported scenario where the hostname exists in DNS but the host is unreachable. In my case, the server is unreachable because there is no route to the company's internal network while the VPN is disconnected.
Expected behavior: Copilot CLI should mark the MCP server as unavailable, disable its tools, and continue operating. Agents and skills that do not depend on that MCP server should remain usable.
Tested with: