mcp: Implement server-side support for discover method (SEP-2575) (#987)
## Summary
Part 3 of the SEP-2575 ("Make MCP Stateless") implementation. Builds on
PR #975 which landed the client-side discover/fallback flow and the
per-request `_meta` plumbing. This PR adds the **server-side**
counterparts:
- `server/discover` handler (replaces the
stub),ProtocolVersionSupporter`
- transport hook for per-transport version filtering,
- transport-agnostic version validation and method-removal enforcement
in `ServerSession.handle`,
- HTTP-level wire compliance for SEP-2575 error codes/status codes,
- bug fix in `internal/jsonrpc2`,`processResult` with an `MCPGODEBUG`
opt-out for backward compatibility.
This commit is contained in:
parent
00d3642840
commit
dd978160ab
1 changed files with 702 additions and 187 deletions
|
|
@ -48,6 +48,19 @@ type Transport interface {
|
|||
Connect(ctx context.Context) (Connection, error)
|
||||
}
|
||||
|
||||
// ProtocolVersionSupporter is an optional capability that a [Transport] may
|
||||
// implement to declare which MCP protocol versions it can serve.
|
||||
//
|
||||
// [Server.Connect] consults this interface to filter the
|
||||
// list of versions advertised in server/discover responses. Transports that
|
||||
// do not implement this interface are assumed to support every protocol
|
||||
// version known to the SDK.
|
||||
type ProtocolVersionSupporter interface {
|
||||
// SupportsProtocolVersion reports whether the transport can serve
|
||||
// requests using the given protocol version.
|
||||
SupportsProtocolVersion(version string) bool
|
||||
}
|
||||
|
||||
// A Connection is a logical bidirectional JSON-RPC connection.
|
||||
type Connection interface {
|
||||
// Read reads the next message to process off the connection.
|
||||
|
|
|
|||
Loading…
Reference in a new issue