8704137635<!-- Provide a brief summary of your changes -->
Update the Go interceptor SDK to use
`github.com/modelcontextprotocol/go-sdk` v1.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:
```
// before
ext.Install(mcpServer)
// after
if err := ext.Install(mcpServer); err != nil {
return err
}
```
New helper added:
```
extension.RegisterSendingMethods(client *mcp.Client) error
```
## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
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?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->
- `go test -v ./...`
## Breaking Changes
<!-- Will users need to update their code or configurations? -->
```go
if err := ext.Install(mcpServer); err != nil {
return err
}
```
The Go SDK module now requires Go 1.25 via
github.com/modelcontextprotocol/go-sdk v1.7.0.
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [x] Breaking change (fix or feature that would cause existing
functionality to change)
- [x] Documentation update
## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [x] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [x] My code follows the repository's style guidelines
- [x] New and existing tests pass locally
- [x] I have added appropriate error handling
- [x] I have added or updated documentation as needed
## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->
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.
Signed-off-by: Ukjae Jeong <jeongukjae@gmail.com>
36 lines
1.3 KiB
Go
36 lines
1.3 KiB
Go
// Copyright 2025 The MCP Interceptors Authors. All rights reserved.
|
|
// Use of this source code is governed by an Apache-2.0
|
|
// license that can be found in the LICENSE file.
|
|
|
|
// Package gomiddleware provides an optional MCP middleware that
|
|
// automatically executes interceptors for every matching
|
|
// request/response. It uses the [chain.Chain] from the
|
|
// [interceptors/chain] package, which invokes interceptors via
|
|
// interceptor/invoke RPCs per the SEP execution model.
|
|
//
|
|
// The middleware is installed on an [mcp.Server] via
|
|
// [mcp.Server.AddReceivingMiddleware]. It marshals request params
|
|
// and response results to [json.RawMessage], calls
|
|
// [chain.Chain.Execute], and applies any mutated payloads back to
|
|
// the request or response.
|
|
//
|
|
// # Usage
|
|
//
|
|
// // Create interceptor extension (exposes interceptors as custom methods)
|
|
// ext := extension.New()
|
|
// ext.AddInterceptor(myValidator)
|
|
// ext.AddInterceptor(myMutator)
|
|
// if err := ext.Install(mcpServer); err != nil {
|
|
// return err
|
|
// }
|
|
//
|
|
// // Create chain via in-memory transport
|
|
// chain, err := ext.LocalChain(ctx, mcpServer)
|
|
//
|
|
// // Install middleware for automatic execution
|
|
// mcpServer.AddReceivingMiddleware(
|
|
// gomiddleware.Middleware(chain,
|
|
// gomiddleware.WithLogger(logger),
|
|
// ),
|
|
// )
|
|
package gomiddleware
|