Evaluate SDK middleware for history/tracing

[olaservo]

Context

TypeScript SDK PR modelcontextprotocol#1406 adds message middleware support:
modelcontextprotocol/typescript-sdk#1406

This adds sendMiddleware and receiveMiddleware options to Protocol, allowing transformation of JSON-RPC messages before sending and after receiving.

Potential Uses in Inspector V2

Use Case	How Middleware Helps
History capture	receiveMiddleware could capture all messages for History page without modifying client logic
Request tracing	sendMiddleware could inject trace IDs for parent-child correlation
Protocol extensions	Add custom capabilities to initialize (e.g., inspector metadata)
Plugin architecture	Plugins could register middleware to intercept/modify messages
Debugging	Inject timestamps, add debugging headers

Action Items

• Monitor PR Tools/prompts/resources vanish on connect: capability gate races the connect event modelcontextprotocol/inspector#1406 for merge
• When merged, evaluate integration into McpContext.tsx
• Consider for request trace model (linking tool calls to sampling requests)
• Evaluate for plugin hooks in client features PR

Related

• PR feat(client): add Mantine UI with MCP SDK integration modelcontextprotocol/inspector#1022 (Mantine UI) - current McpContext uses direct SDK connection
• PR spec: Add client features UX patterns (sampling/elicitation) modelcontextprotocol/inspector#1011 (client features UX spec) - request trace model spec
• Issue Inspector V2 Data Spec modelcontextprotocol/inspector#983 (data spec) - history/logging architecture

[olaservo]

Moving to upstream repo