microsoft / microsoft/copilot-for-eclipse

MCP server connection failure should not show a blocking dialog

Open
#88 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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

Eclipse IDE for Enterprise Java and Web Developers 2026-03 M2

Platform

Linux mars 6.18.7-1-default #1 SMP PREEMPT_DYNAMIC Fri Jan 23 12:13:24 UTC 2026 (14faf12) x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce

In the Eclipse preferences navigate to GitHub Copilot → Model Context Protocol and define a server that is not reachable, for example:

{
  "servers": {
     "missing": {
      "type": "streamable-http",
      "url": "http://localhost:54321/"
   }
}
Logs (optional)

No response

Expected behavior

A remote MCP server that is not available should be indicated in the UI in a non-obtrusive way. Popping up a dialog interrupts the flow at startup and is not desired.

I actually managed to deadlock my Eclipse by clicking Help → About and then when the MCP server unavailable dialog popped up I was unable to close either of then.

Actual behavior

A dialog pops up unconditionally at startup.

Image
Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue from Eclipse preferences under GitHub Copilot → Model Context Protocol using an unreachable streamable-HTTP server such as http://localhost:54321/. Trace the startup path that produces the unavailable-server dialog; done means the failure is indicated non-obtrusively without a blocking dialog.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.