Connect to an existing MATLAB engine

[yanndebray]

The title of this issue is the main feature required to nicely integrate into VSCode, when the MATLAB extension for VSCode is installed.
This capability is also useful in other contexts (such as running in GitHub Codespaces) and called from other host applications (VSCode-forks such as Cursor or Windsurf).

The workflow is the following for a project that doesn't start from scratch:

• Open a m. file starts another session of MATLAB
• From there, the expectation is for the MATLAB extension for VSCode to provide the MATLAB MCP Core Server with informations about the MATLAB session started to connect to it instead of starting a separate one at the first tool call in the chat panel.

The reverse workflow also surfaces as a sub-requirement to enable the MATLAB extension for VSCode to reuse the MATLAB session started by the MATLAB MCP Core Server (either on first start when setting up the server, or on subsequent VSCode sessions upon first tool call).

Similar issues will appear with the use of Jupyter notebooks in VSCode, that will trigger the start of a third session of MATLAB in this case.

[agoldsbo]

Thank you for the enhancement and detailed description! We will take this into consideration as we continue to develop the MCP server.

[Ebola-Chan-bot]

This feature is very important. It's weird to start a new MATLAB session every time.