You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
error when using path variables in memory file configuration #1846
I have the same issue. variable references like ${workspaceFolder} cannot be resolved strangely in this case. I have the same issue with relative paths. The only workaround that works for me is using an absolute path which isn't ideal since I prefer to have the MCP servers configured in the user settings and therefore multiple projects share the same file.
${workspaceFolder} is a client-side variable; the server receives whatever string the client puts in the environment. VS Code now substitutes it in mcp.json, and Claude Desktop does not support variables at all. The relative-path behaviour mentioned in the follow-up is #692, which #4327 fixes. Closing this one.
Activity
sascharo commentedon Jun 4, 2025
I have the same issue. variable references like
${workspaceFolder}cannot be resolved strangely in this case. I have the same issue with relative paths. The only workaround that works for me is using an absolute path which isn't ideal since I prefer to have the MCP servers configured in the user settings and therefore multiple projects share the same file.@KingOfTac, have you found a solution?
sascharo commentedon Jun 4, 2025
#1600, #1481 and #1018 seem to be related or actual the same issue.
olaservo commentedon Sep 3, 2026
${workspaceFolder}is a client-side variable; the server receives whatever string the client puts in the environment. VS Code now substitutes it inmcp.json, and Claude Desktop does not support variables at all. The relative-path behaviour mentioned in the follow-up is #692, which #4327 fixes. Closing this one.