Description

Imagine a scenario where my resources are a set of notes returned by an API. When I use server.AddResource, the order (reverse or chronological) in which ListResources retrieves them should reflect my notes' updates. I see that mcp-go uses an internal map during server.AddResource, which clearly loses the sorting logic.