VSCode Profiles do not inherit the default mcp.json from the install process

[voidburn]

Not sure if it's because I had the profiles prior to installing them, or this was a honest oversight.

It wasn't working after the install command (everything was in place, detected all installed tools correctly), so I:

1. inspected the mcp.json file in ~/Library/Application\ Support/Code/User/mcp.json -> present
2. Listed available MCP servers with >MCP: list servers command in vscode (none showed up)
3. proceeded to add a new one as a global MCP server using the command above (passed it the same data present in the installed mcp.json installed)
4. Noticed that it was now correctly detected:
5. Ran a find in the filesystem to see where it was added and realized that profiles had their own, in my cae it was put in the active profile: ~/Library/Application\ Support/Code/User/profiles/5552b383/mcp.json

I'm not sure if the install process should worry about deploying the mcp.json in every detected profile, but I would definitely add a prominent note in the appropriate section of the install process of the README.md file concerning VSCode, so that new users with a setup similar as mine can immediately enjoy this fantastic piece of software.

Thank you for your amazing work of passion,

absolutely loving it!

[DeusData]

Thanks for highlighting, will check once there is time :)