Automated port handling with multiple workspaces.

[yeroc]

Is there any way that this extension could automatically allocate different ports for separate workspaces and then expose that port number somehow to a cli utility that could then adjust MCP server config appropriately. I use new VS Code workspace windows every day (sometimes multiple) because I use git work-trees to keep changes separated. I find this generally works very well but it makes extensions like this unusable because the management of separate port numbers becomes such a burden. I don't yet have great ideas on how to make this work automatically but I'm curious whether others have given this any thought.

[biegehydra]

I can automatically generate a port by performing some sort of hash on the directory or workspace name, but that doesn't solve the problem. Because you will still have to figure out what that port is and add it to cursor, windsurf, or whatever you use

[yeroc]

@biegehydra Thanks for responding. If the VS Code extension could add the port number to an environment variable similar to what VS Code itself does then I can add a simple wrapper script that updates the mcp config when launching claude code from a terminal inside VS Code.