microsoft / microsoft/copilot-for-eclipse
Problems reconnecting MCP or changing MCP IP Address
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 126
- Forks
- 60
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 5
Description
Feedback source
None
GitHub Copilot plugin version
0.15.0.202601270459
Eclipse IDE and version
Version: 2025-12 (4.38.0) Build id: 20251204-0850
Platform
Linux 6.8.0-1048-gke microsoft/copilot-for-eclipse#51-Ubuntu SMP Fri Mar 6 12:03:00 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
Steps to reproduce
configure an external MCP Server, start eclipse while the server is down, start the mcp server, wont reconnect automatically, even going to copilot->Preferences and apply.
Only way is by changing server name.
Similar problem if you run eclipse and discover that the machine running mcp server has a different url, if you change in copilot->Preference->Server configuration the url of mcp server, the apply, eclipse try to connect to old url
Logs (optional)
No response
Expected behavior
Check for disconnected mcp server when pressing apply, and update mcp server url if it's changed in configuration.
Actual behavior
Actually wont try to reconnect or try to reconnect at original url, and wont follow changes.
Additional information
I'm working on a local mcp server for code documentation so it's on a different machine on the same network and sometimes change ip or sometime isn't running the mcp app when starting eclipse.
Not a really a big problem when in production with a fixed address for the server i think.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce with an external MCP server stopped before Eclipse starts, then use Copilot > Preferences > Server configuration after starting it. Verify that applying the configuration reconnects to the server and that changing its URL makes Eclipse use the new address rather than the original one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100