Skip to content

docs: fix four dead links to the Multi Round-Trip Requests section #1159

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.

Sign up for GitHub

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

Merged
guglielmo-san merged 1 commit into from
Aug 13, 2026
+8 −8
Merged

docs: fix four dead links to the Multi Round-Trip Requests section #1159

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/client.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ method. To receive notifications about root changes, set
[`ServerOptions.RootsListChangedHandler`](https://pkg.go.dev/github.com/modelcontextprotocol/go-sdk/mcp#ServerOptions.RootsListChangedHandler).
For protocol versions `2026-07-28` and later, `ListRoots` requests are
delivered via the
[Multi Round-Trip Requests](protocol.md#multi-round-trip-requests-mrtr)
[Multi Round-Trip Requests](#multi-round-trip-requests)
pattern.

```go
Expand Down Expand Up @@ -113,7 +113,7 @@ This function is invoked whenever the server requests sampling.

For protocol versions `2026-07-28` and later, sampling requests are
delivered via the
[Multi Round-Trip Requests](protocol.md#multi-round-trip-requests-mrtr)
[Multi Round-Trip Requests](#multi-round-trip-requests)
pattern.

```go
Expand Down Expand Up @@ -183,7 +183,7 @@ you must declare that capability explicitly (see [Capabilities](#capabilities))

For protocol versions `2026-07-28` and later, elicitation requests are
delivered via the
[Multi Round-Trip Requests](protocol.md#multi-round-trip-requests-mrtr)
[Multi Round-Trip Requests](#multi-round-trip-requests)
pattern.

```go
Expand Down Expand Up @@ -268,7 +268,7 @@ For legacy (`<= 2025-11-25`) servers, the SDK transparently sends server
requests on the legacy server-initiated channel; the MRTR machinery is a
no-op in that direction. For legacy clients talking to MRTR-style servers,
the server SDK applies the inverse compatibility shim — see the
[server-side documentation](server.md#multi-round-trip-requests-mrtr).
[server-side documentation](server.md#multi-round-trip-requests).

## Capabilities

Expand Down
8 changes: 4 additions & 4 deletions internal/docs/client.src.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ method. To receive notifications about root changes, set
[`ServerOptions.RootsListChangedHandler`](https://pkg.go.dev/github.com/modelcontextprotocol/go-sdk/mcp#ServerOptions.RootsListChangedHandler).
For protocol versions `2026-07-28` and later, `ListRoots` requests are
delivered via the
[Multi Round-Trip Requests](protocol.md#multi-round-trip-requests-mrtr)
[Multi Round-Trip Requests](#multi-round-trip-requests)
pattern.

%include ../../mcp/client_example_test.go roots -
Expand All @@ -57,7 +57,7 @@ This function is invoked whenever the server requests sampling.

For protocol versions `2026-07-28` and later, sampling requests are
delivered via the
[Multi Round-Trip Requests](protocol.md#multi-round-trip-requests-mrtr)
[Multi Round-Trip Requests](#multi-round-trip-requests)
pattern.

%include ../../mcp/client_example_test.go sampling -
Expand All @@ -79,7 +79,7 @@ you must declare that capability explicitly (see [Capabilities](#capabilities))

For protocol versions `2026-07-28` and later, elicitation requests are
delivered via the
[Multi Round-Trip Requests](protocol.md#multi-round-trip-requests-mrtr)
[Multi Round-Trip Requests](#multi-round-trip-requests)
pattern.

%include ../../mcp/client_example_test.go elicitation -
Expand Down Expand Up @@ -117,7 +117,7 @@ For legacy (`<= 2025-11-25`) servers, the SDK transparently sends server
requests on the legacy server-initiated channel; the MRTR machinery is a
no-op in that direction. For legacy clients talking to MRTR-style servers,
the server SDK applies the inverse compatibility shim — see the
[server-side documentation](server.md#multi-round-trip-requests-mrtr).
[server-side documentation](server.md#multi-round-trip-requests).

## Capabilities

Expand Down
Loading