-
Notifications
You must be signed in to change notification settings - Fork 3.2k
feat: adds cwd to the MCP yaml as an option. #6280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for continuedev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
✨ No issues found! Your code is sparkling clean! ✨ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, thanks for the tests + docs
🎉 This PR is included in version 1.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Now users can configure MCP servers with a current working directory (cwd):
The implementation supports:
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
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.