Currently the MCP server is bundled in the VSCode extension. This forces users to use VSCode for the MCP abilities.
I suggest to create another offering of the DebugMCP core logic, that will be served as a standalone MCP server.
One challenge I see here is how to manage the different debuggers, previously easy to reach via DAP against VSCode (since the common pattern is that users install a language-specific extensions that adds a debugger under the hood, which then VSCode exposes via DAP).
Currently the MCP server is bundled in the VSCode extension. This forces users to use VSCode for the MCP abilities.
I suggest to create another offering of the DebugMCP core logic, that will be served as a standalone MCP server.
One challenge I see here is how to manage the different debuggers, previously easy to reach via DAP against VSCode (since the common pattern is that users install a language-specific extensions that adds a debugger under the hood, which then VSCode exposes via DAP).