Problem
MCP handlers need the metadata from the current request to read values such as progressToken. The server client context currently exposes initialization data, but not the current request's _meta.
The external tools-call-with-progress conformance scenario exposes this gap.
Observed behavior
A tool handler cannot obtain the active call's progress token through McpRequestContext, so it cannot associate notifications/progress messages with the request being processed.
Expected behavior
The invocation context should expose the decoded metadata belonging to the current request. A tool should be able to read the supplied progress token and emit correctly correlated progress notifications.
Regression coverage
Add an adapter test that initializes a client, calls a tool with a distinct _meta.progressToken, and asserts that the handler sees that call-level token rather than initialization metadata or undefined.
Problem
MCP handlers need the metadata from the current request to read values such as
progressToken. The server client context currently exposes initialization data, but not the current request's_meta.The external
tools-call-with-progressconformance scenario exposes this gap.Observed behavior
A tool handler cannot obtain the active call's progress token through
McpRequestContext, so it cannot associatenotifications/progressmessages with the request being processed.Expected behavior
The invocation context should expose the decoded metadata belonging to the current request. A tool should be able to read the supplied progress token and emit correctly correlated progress notifications.
Regression coverage
Add an adapter test that initializes a client, calls a tool with a distinct
_meta.progressToken, and asserts that the handler sees that call-level token rather than initialization metadata orundefined.