feat: adds cwd to the MCP yaml as an option.

[bdougie]

Description

Now users can configure MCP servers with a current working directory (cwd):

  mcpServers:
    - name: my-project-server
      command: npm
      args: ["run", "mcp-server"]
      cwd: "/path/to/my/project" # this field is new
      env:
        NODE_ENV: "production"

The implementation supports:

• Absolute paths: /Users/developer/project
• Relative paths: ./my-project or ../servers
• Optional usage (backward compatible)

The cwd option will be passed directly to the StdioClientTransport, allowing MCP servers to run in their intended working directory context.

This work unblocks the work I am doing with LanceDB in this repo

https://github.com/bdougie/git_blame_search/?tab=readme-ov-file#continue-integration

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

Screenshots

[ For visual changes, include screenshots. Screen recordings are particularly helpful, and appreciated! ]

Tests

Note the tests were generated using Claude. cc @uinstinct for a look to see if they match the work you've already done.

The tests confirm that the cwd is not required and successfully transports the MCP to the current directory.

[netlify]

✅ Deploy Preview for continuedev canceled.

Name	Link
🔨 Latest commit	e662a66
🔍 Latest deploy log	https://app.netlify.com/projects/continuedev/deploys/685d3b12aae3650008190832

[recurseml]

⚠️ Only 5 files will be analyzed due to processing limits.

[recurseml]

✨ No issues found! Your code is sparkling clean! ✨