Usage and Thraed Safety of McpAsyncClient

[jonasbbin]

Pre-submission Checklist

• I have checked that this question would not be more appropriate as an issue in a specific repository
• I have searched existing discussions and documentation for answers

Question Category

• Protocol Specification
• SDK Usage
• Server Implementation
• General Implementation
• Documentation
• Other

Your Question

I am a bit unsure on how the MCP Client should be used in an application that runs an agent concurrently. (E.g. Summarizing a book by summarizing each chapter concurrently). Following the example: Is the idea that each Chapter summarizing call should have its own McpAsyncClient? It feels a bit weird to have multiple instances of an McpAsyncClient for the same agent. On the other Hand I was unsure if stateful MCP features like sampling would be thread safe.

Is there an official guideline? I couldn't find information about this.

[jialiuyang]

its one json-rpc session request ids are unique pendingResponses is ConcurrentHashMap so parallel callTool is intended

sampling rides the same session keep your sampling handler thread-safe the client itself is fine

if the server keeps cwd or open files concurrent mutating tools can still collide thats the server for chapter summarize one client is enough dont new a client per chapter thats just extra initialize