[explyt MCP] client tears down built-in IDE MCP Server: No ContextAccessor for contextType react

## Observed symptom [BUG] MCP client tears down the built-in IDE MCP Server session: No ContextAccessor for contextType reactor.util.context.Context1 (regression from #86) ### Problem details The built-in MCP client cannot list tools for the IDE's own built-in MCP server (`IDE MCP Server`): the session is established, `tools/list` is answered, and the client then tears the session down with ``` java.lang.IllegalStateException: No ContextAccessor for contextType: class reactor.util.context.Context1 ``` The MCP panel reports this as `Cannot List Tools` / `Tools Endpoint Failed` ("the server could not provide its list of available tools"). The server itself is healthy — it is the client-side reactor context that breaks. This is a regression: a report with the same exception (#86, plugin 5.4.0) was closed in March as expected-fixed in 5.5, so the `No ContextAc ## Literal error text ``` No ContextAccessor for contextType react ``` ## Environment GitHub issue explyt/explyt #100 ## Trigger / context ### Problem details The built-in MCP client cannot list tools for the IDE's own built-in MCP server (`IDE MCP Server`): the session is established, `tools/list` is answered, and the client then tears the session down with ``` java.lang.IllegalStateException: No ContextAccessor for contextType: class reactor.util.context.Context1 ``` The MCP panel reports this as `Cannot List Tools` / `Tools Endpoint Failed` ("the server could not provide its list of available tools"). The server itself is healthy — it is the client-side reactor context that breaks. This is a regression: a report with the same exception (#86, plugin 5.4.0) was closed in March as expected-fixed in 5.5, so the `No ContextAccessor` failure is back in 5.20.1. ### Steps to reproduce 1. Have the bundled IDE MCP server enabled (Settings → Tools → MCP Server, `enableMcpServer = true`). 2. Let the agent auto-connect to the `IDE MCP Server` entry (or reconnect it from the MCP panel). 3. The server initializes and answers, then the session is dropped and the MCP panel shows `Cannot List Tools`. Reproduced deterministically: twice in a row after enabling the built-in IDE MCP server, and again after an explicit reconnect. ## Source evidence - https://github.com/explyt/explyt/issues/100 (2026-09-29T15:41:21Z) — #100 ## Freshness - classification: FRESH_7D - retrieved_at: 2026-10-02T09:46:06.809152Z - scout_id: C479d26e3d3 ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome.