Repository navigation
VSCode Profiles do not inherit the default mcp.json from the install process #431
Description
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:
- inspected the
mcp.jsonfile in~/Library/Application\ Support/Code/User/mcp.json-> present - Listed available MCP servers with
>MCP: list serverscommand in vscode (none showed up) - 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)
- Noticed that it was now correctly detected:
- 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!
Activity
DeusData commentedon Jun 9, 2026
Thanks for highlighting, will check once there is time :)
test(repro): install/UX reproductions for #570, #409, #431
DeusData commentedon Jun 28, 2026
This issue now has a first-class, durable reproduction in the cumulative bug-reproduction suite landing in #667 — a test that pins the exact failing behaviour, so it's tracked and guarded against silent regression. Where #667 also lands the root-cause fix, that's called out in the PR; otherwise the reproduction makes the eventual fix straightforward and verifiable.
The reproduction goes live once #667 merges. (Posted from the release branch's QA pass.)
fix: 17 reproduce-first issue + new-bug fixes (per-case verified)
test(repro): honest-RED #581, honest safety-net #431 (false-guard audit)
DeusData commentedon Aug 21, 2026
Thank you again for the clear report and the concrete profile path. Current main now scans Code/User/profiles and installs or updates mcp.json for every existing VS Code profile directory, in addition to the default user configuration. The dedicated issue 431 reproduction passes on the current head.
I am closing this as fixed. If a current build still misses an existing profile, please reopen the issue with the OS, VS Code version, and profile-directory layout, and we will investigate further.