Diogo Santos

> > > I have successfully compiled this on windows using MSys2/MingW64 using the following commands: > > ``` > git clone https://github.com/Ironholds/poster.git > cd poster > ``` > >...

Thanks for opening this — having sensible timeout behavior is critical for production MCP usage, especially when LLMs are orchestrating many tool calls. From a broader SDK perspective, there are...

This is a great issue to surface — from a broader perspective, the SDK could benefit from a more consistent error **taxonomy** and cross-layer behavior, not just in `ClientSession`. A...

I’d like to +1 this and suggest a slightly more structured approach that could make observability easier to adopt across MCP deployments. Concretely, it might help to: 1. Add a...

Updated the instrumentation interface to use a token-based API based on [community feedback](https://github.com/modelcontextprotocol/python-sdk/issues/421#issuecomment-3589299995). This enables proper OpenTelemetry integration without external storage. See updated PR description for details.

Linking this to the ongoing protocol work around discovery/filtering (e.g. https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1300 and related scope/versioning SEPs). From a host/client perspective, once `tools/list` (and friends) gain richer filtering in the spec –...

Small note connecting this to the broader work on tool versioning. This proposal is related to, but distinct from, https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1766: * **[#1766](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1766)** focuses on *identifying and pinning specific tool versions*...