Go SDK: Upgrade MCP SDK and remove vendored copy - #35
Open
jeongukjae wants to merge 1 commit into
Open
Conversation
Signed-off-by: Ukjae Jeong <jeongukjae@gmail.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Update the Go interceptor SDK to use
github.com/modelcontextprotocol/go-sdkv1.7.0 custom method APIs and remove the vendored Go SDK copy. This shouldn't update the behaviours, but addding following functions.Changed public/user-facing interfaces:
extension.Extension.Install now returns an error:
New helper added:
Motivation and Context
Pick up MCP Go SDK 1.7.0. This provides upstream custom method support, so the local vendored SDK copy is no longer needed.
How Has This Been Tested?
go test -v ./...Breaking Changes
The Go SDK module now requires Go 1.25 via github.com/modelcontextprotocol/go-sdk v1.7.0.
Types of changes
Checklist
Additional context
LocalChain now registers interceptor custom sending methods internally. Manual remote chain setup should call
extension.RegisterSendingMethods(client)before connecting the MCP client session used with chain.AddMCPServer.