feat: allow the client version to be set from the user in the experimental_createMCPClient #10398
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
.changeset/tender-cups-shout.md
Outdated
| '@ai-sdk/mcp': patch | ||
| --- | ||
|
|
||
| Add the possibility to define client version in mcp client definition |
Contributor
There was a problem hiding this comment.
It looks like the majority of the change set files follow conventional commits semantics, although I’m not sure if there are any specific rules behind it. Cant find anything about it in the CONTRIBUTING.md
Contributor
Author
There was a problem hiding this comment.
Thanks for the feedback - updated the file then :)
aayush-kapoor
requested changes
Nov 24, 2025
Contributor
aayush-kapoor
left a comment
aayush-kapoor
left a comment
There was a problem hiding this comment.
changes look good but just edit the changeset file
…ibility-to-set-client-version
…ibility-to-set-client-version
Contributor
|
@qchuchu can you also look into the failing CI tests? thanks |
…ibility-to-set-client-version
aayush-kapoor
approved these changes
Nov 24, 2025
vercel-ai-sdk bot
pushed a commit
that referenced
this pull request
Nov 24, 2025
…ental_createMCPClient (#10398) ## Background The MCP client was using a hardcoded client version ('1.0.0') that couldn't be customized by users. This prevented users from setting their own client version when creating an MCP client instance, which may be needed for version tracking, compatibility requirements, or integration with specific MCP servers. ## Summary Added an optional version parameter to MCPClientConfig interface that allows users to set a custom client version when creating an MCP client. The parameter defaults to '1.0.0' (the existing CLIENT_VERSION constant) to maintain backward compatibility. **Changes**: - Added optional version property to MCPClientConfig interface with JSDoc documentation - Updated DefaultMCPClient constructor to accept version parameter with default value - Modified clientInfo assignment to use the provided version instead of hardcoded CLIENT_VERSION ## Manual Verification Created an MCP client with a custom version and verified that: 1. The client initializes successfully with the custom version 2. The client version is correctly set in the clientInfo object 3. Existing code without the version parameter continues to work with the default '1.0.0' version ## Checklist <!-- Do not edit this list. Leave items unchecked that don't apply. If you need to track subtasks, create a new "## Tasks" section Please check if the PR fulfills the following requirements: --> - [X] Tests have been added / updated (for bug fixes / features) - [ ] Documentation has been added / updated (for bug fixes / features) - [X] A _patch_ changeset for relevant packages has been added (for bug fixes / features - run `pnpm changeset` in the project root) - [X] I have reviewed this pull request (self-review) --------- Co-authored-by: josh <[email protected]> Co-authored-by: Aayush Kapoor <[email protected]>
Contributor
|
✅ Backport PR created: #10562 |
vercel-ai-sdk bot
added a commit
that referenced
this pull request
Nov 24, 2025
…he experimental_createMCPClient (#10562) This is an automated backport of #10398 to the release-v5.0 branch. FYI @qchuchu Co-authored-by: Quentin Churet <[email protected]> Co-authored-by: josh <[email protected]> Co-authored-by: Aayush Kapoor <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
The MCP client was using a hardcoded client version ('1.0.0') that couldn't be customized by users. This prevented users from setting their own client version when creating an MCP client instance, which may be needed for version tracking, compatibility requirements, or integration with specific MCP servers.
Summary
Added an optional version parameter to MCPClientConfig interface that allows users to set a custom client version when creating an MCP client. The parameter defaults to '1.0.0' (the existing CLIENT_VERSION constant) to maintain backward compatibility. Changes:
Manual Verification
Created an MCP client with a custom version and verified that:
Checklist
pnpm changesetin the project root)