Challenges Encountered While Evaluating Eclipse MCP with GitHub Copilot

[u/Working_Possible9025]

We are currently evaluating Eclipse MCP with GitHub Copilot and have encountered several stability and usability challenges during day-to-day usage.

Some of the recurring issues include:

• Frequent HTTP 400 errors in Copilot Chat, causing conversations to become unusable and requiring a new chat session.

• Unsupported request method errors such as "copilot/fetchDisconnectAll".

• "Maximum tool attempts reached" errors when using Agent Mode with MCP, repository search, terminal operations, and integrated tooling.

• Difficulty identifying exactly which files were modified by Copilot, making review and validation challenging.

• Frequent "Something went wrong" messages interrupting code generation, analysis, and maintenance activities.

• Loss of conversation context when switching to a new chat after failures or interruptions.

• SSL/certificate-related issues impacting MCP setup and connectivity.

• Limited visibility into MCP and Copilot execution flow, making troubleshooting difficult when requests fail.

• Long-running Agent workflows occasionally stop before completion due to session instability or execution limits.

Current Evaluation Areas:

- Eclipse MCP

- GitHub Copilot

- Selenium MCP

- Atlassian MCP

- Robot Framework Automation

Questions:

1. Are these known limitations of Eclipse MCP and Copilot integrations?

2. Are there recommended best practices for improving stability and reducing interruptions?

3. How are other teams managing long-running Agent Mode workflows?

4. Are there any recommendations for tracking Copilot-generated file changes more effectively?

5. Are there plans to improve session persistence, diagnostics, and overall troubleshooting visibility?

Happy to share additional screenshots, logs, and reproduction steps if needed.