feat: Adjusted MCPConnection logic so the cwd is resolved to current workspace folder.

[meanderix]

Description

It was made possible specifiying a current working directory (cwd) for mcp servers in the following PR.

However, unless cwd is manually set in the MCP server definition itself, there is no way for the MCP server to resolve cwd to the current workspace directory. This causes issues with some of the original Anthropic MCP servers, such as mcp-server-git. See #7173.

The following PR attempts to adjust the logic so that unless cwd is manually set, we use the workspace folder. (As far as I can tell, unless we do this, the cwd is actually resolved to path of the vscode binary.)

This makes mcp-server-git (and other mcp servers) work in multiple projects without having to manually update cwd.

AI Code Review

• Team members only: AI review runs automatically when PR is opened or marked ready for review
• Team members can also trigger a review by commenting @continue-general-review or @continue-detailed-review

Checklist

• I've read the contributing guide
• The relevant docs, if any, have been updated or created
• The relevant tests, if any, have been updated or created

Tests

---

Summary by cubic

Default MCP server cwd to the current workspace root when not explicitly set. This fixes path resolution issues and lets servers like mcp-server-git work across projects without manual config.

• Bug Fixes
  • Resolve cwd from IDE workspace dirs when not provided.
  • Preserve user-provided cwd as-is.
  • Avoids defaulting to the VS Code binary path.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[meanderix]

An open question would be how to handle manually specified relative paths. Do we want them to be relative to the vscode folder or to the workspace folder?

[meanderix]

recheck

[meanderix]

I have read the CLA Document and I hereby sign the CLA

[RomneyDa]

@meanderix relative paths (no leading slash) can be resolved using the resolveRelativePathInDir util

[RomneyDa]

@meanderix could you also add unit tests for this to validate expected behavior on various platforms etc?

[meanderix]

@RomneyDa I'll take a look at that.

[Patrick-Erichsen]

Quick bump on this @meanderix , would be great to get it in!

[meanderix]

@Patrick-Erichsen @RomneyDa I've refactored the code a bit and added tests. Let me know what you think.

[Patrick-Erichsen]

This worked for me locally, there are a few merge conflicts now unfortunately. @meanderix if you can get those resolved this is good to merge!

[RomneyDa]

@meanderix the merge conflicts were ugly and caused by me. took a swing at fixing.

[sestinj]

🎉 This PR is included in version 1.27.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.24.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀