[Bug] Failed to initialize MCP server 'abap-mcp'

[waan-Rational]

Environment

• OS: Windows
• Eclipse Version: Version: 2026-06 (4.40.0) Build id: 20260604-0653
• Plugin Version:
  • GitHub Copilot for Eclipse: 0.20.0.202607100822
  • ABAP Development Tools: 3.60.0

Describe the bug
GitHub Copilot for Eclipse tries to initialize the configured MCP server abap-mcp immediately during Eclipse startup, before the ABAP system logon has completed and before the ABAP MCP Server provided by ABAP Development Tools is available.

As a result, GitHub Copilot shows the following startup error:

Failed to initialize MCP server 'abap-mcp'. Please check the logs for more details.

The Eclipse Error Log shows that GitHub Copilot tries to connect to the ABAP MCP endpoint too early:

[CopilotMCP] Error initializing MCP server abap-mcp: FetchError
[CopilotMCP] Connection failed: FetchError
[CopilotMCP] MCP server abap-mcp error: FetchError
[fetcher] Request to http://localhost:2234/mcp failed, attempting fallback. Error [TypeError]: fetch failed

The issue appears to be a startup lifecycle/race condition: the GitHub Copilot Language Server starts and initializes configured MCP servers before the ABAP MCP Server is started by ADT after ABAP system logon.

To Reproduce
Steps to reproduce the behavior:

1. Enable the ABAP MCP Server in ADT under:

   Window -> Preferences -> ABAP Development -> MCP Server

2. Configure an MCP server named abap-mcp in GitHub Copilot for Eclipse, for example:

   {
     "servers": {
       "abap-mcp": {
         "url": "http://localhost:2234/mcp",
         "requestInit": {
           "headers": {
             "Authorization": "Bearer <ADT_MCP_TOKEN>"
           }
         }
       }
     }
   }

3. Restart Eclipse.

4. While the ABAP logon is still running and ADT is retrieving compatibility information from the backend system, GitHub Copilot already tries to initialize the abap-mcp MCP server.

5. See the popup error:

   Failed to initialize MCP server 'abap-mcp'. Please check the logs for more details.

6. Open the Eclipse Error Log and observe entries similar to:

   [CopilotMCP] Error initializing MCP server abap-mcp: FetchError
   [CopilotMCP] Connection failed: FetchError
   [fetcher] Request to http://localhost:2234/mcp failed, attempting fallback. Error [TypeError]: fetch failed

Expected behavior
GitHub Copilot for Eclipse should not show an error popup during startup if a configured MCP server is temporarily unavailable because another Eclipse plugin has not finished initialization yet.

Expected behavior would be one of the following:

• GitHub Copilot should delay initialization of MCP servers until Eclipse startup and dependent plugin initialization are complete.
• GitHub Copilot should retry connecting to the MCP server after a short delay.
• GitHub Copilot should initialize MCP servers lazily only when Agent Mode or MCP tools are used.
• GitHub Copilot should allow a configured MCP server to be marked as optional or manually started, so unavailable local MCP servers do not cause startup error popups.

Screenshots
Screenshots attached:

1. GitHub Copilot Language Server popup:

   Failed to initialize MCP server 'abap-mcp'. Please check the logs for more details.

2. Eclipse Error Log showing:

   [CopilotMCP] Error initializing MCP server abap-mcp: FetchError
   [CopilotMCP] Connection failed: FetchError
   [fetcher] Request to http://localhost:2234/mcp failed, attempting fallback. Error [TypeError]: fetch failed

Additional context
The configured MCP endpoint is:

http://localhost:2234/mcp

The ABAP MCP Server is provided by ABAP Development Tools and appears to become available only after the ABAP system logon and ADT backend initialization have completed.

The error does not necessarily indicate a wrong MCP configuration or invalid token. Instead, the issue seems to occur because GitHub Copilot initializes the abap-mcp server before ADT has started the local ABAP MCP Server.

It would be helpful if GitHub Copilot for Eclipse supported delayed, lazy, retry-based, or manually triggered MCP server initialization for local MCP servers that depend on other Eclipse plugins.

Additional log entries observed:

[CopilotMCP] Failed to auto-start MCP server abap-mcp during first boot: FetchError
[CopilotMCP] MCP server abap-mcp connection closed.
[CopilotMCP] Error initializing MCP server abap-mcp: FetchError
[CopilotMCP] Connection failed: FetchError
[CopilotMCP] MCP server abap-mcp error: FetchError
[fetcher] Request to http://localhost:2234/mcp failed, attempting fallback. Error [TypeError]: fetch failed