copilot-cli icon indicating copy to clipboard operation
copilot-cli copied to clipboard

Copilot suddenly doesn't recognize MCP servers

Open non-stop-dev opened this issue 2 months ago • 4 comments

Describe the bug

Image

I exit and relaunch copilot and still getting same answer, despite it was working previously. This is a new project I just launched, in previous projects where it worked just a few minutes ago, isn't working now neither.

Affected version

0.0.352

Steps to reproduce the behavior

No response

Expected behavior

No response

Additional context

No response

non-stop-dev avatar Oct 28 '25 20:10 non-stop-dev

Updated to the latest version and still same issue

non-stop-dev avatar Oct 28 '25 20:10 non-stop-dev

Well, it works now, don't know what happened but fixed by itself

non-stop-dev avatar Oct 28 '25 21:10 non-stop-dev

Hi @non-stop-dev, I'm glad it fixed itself! Where were these MCP Servers defined? In your local ~/.copilot/mcpconfig?

RyanHecht avatar Oct 28 '25 21:10 RyanHecht

Hi @RyanHecht I think they are in my local ~/.copilot/mcpconfig cause I configured them through /mcp add command, I think MCPs added through that command go to ~/.copilot/mcpconfig.

Don’t know what happened. It suddenly stopped working, I waited like 10-15min and tried again and worked (in the same ongoing chat that failed before).

Worth to mention that I restarted terminal, re opened new conversations, updated, etc. and nothing of that fixed it.

Don’t really know how MCPs work internally with Copilot so no idea what went wrong.

non-stop-dev avatar Oct 29 '25 04:10 non-stop-dev

Hi @RyanHecht . Problem is back again, is like this for a few hours now

Image

non-stop-dev avatar Nov 11 '25 16:11 non-stop-dev

Fixed alone now. I'm guessing if this has to do with BitBucket down today? Or another cloud service related to it.

non-stop-dev avatar Nov 11 '25 20:11 non-stop-dev

Same problem again with the last update v 0.0.358

Image

non-stop-dev avatar Nov 15 '25 20:11 non-stop-dev