BUG: MCP affects other projects when working in two or more editors

[Leuconoe]

Copilot is supposed to apply only to Project A, but there are cases where it ignores this and applies to Project B.

• Reproduction Steps
  Project A - GitHub Copilot
  Project B - Claude Code

While working on Project A, changes to Project B are overwritten.

• Issues Encountered
  Editor settings overwritten
  Submodules forcibly deleted
  Source code overwritten

Is it not recommended to use MCP across two or more projects?
It seemed to be working fine, but this problem suddenly arose.

[Scriptwonder]

Depends on how you use it, stdio multiple ports should be fine, http local currently do have this kind of issue. We are thinking about extending to multiple concurrent dev, so this should be resolved in the future.

Right now a solution could be using A for stdio, and B for http local

[rkdrnf]

Even with stdio, agents are confused finding the exact instance when there're multiple instances.
I'm also seeing that stdio ports are changing / restarting when there're multiple editors

[Scriptwonder]

Yes, this is why we put out http in the first place. On second thought maybe http with different port could help?

We will work on the connection issue for multi-instance multi-port MCP usage for our next big update, so stay tuned.

[gibertoni]

As a workaround I have instructed the AI agent to set an active instance that matches the name of the repository it is working on. The tool to list instances and set active instance already exist