This feature request is the reverse workflow of the one described here:
matlab/matlab-mcp-core-server#9
In the scenario when the MATLAB MCP Core Server creates .m files in an empty project:
- Opening those files after a tool call of the MCP Server will spawn a second MATLAB session
- Here, the expectation is for the MATLAB extension for VSCode to reuse the MATLAB session started by the MCP server
Another workflow that starts a MATLAB session is on the first time the MATLAB MCP Core Server is installed (either globally or for the workspace).