shaun smith

It does thanks @patwhite I think the danger is in overthinking them. A Resource is simply some text or binary data, an identifier (uri) and a mimeType - no more,...

Update 28/04/2025 - I have also updated the server/Resources page to include a sub-section on Custom URI schemes, primarily as the link in the opening paragraph is not obvious.

> I totally get the pitch - if we decouple permanence from the notion of EmbeddedResource, we unlock a bunch of utility and expressive, and RFC 3986 lets us do...

> The problem is that irrespective of RFC 3986, MCP broadly assumes/relies on the persistence of Resources (e.g. the resources/list -> resources/read flow). There's a chance we're overthinking this. The...

Thanks @bhosmer-ant -- should be good, tripped over the lastModified merge. Should be mergeable

What model are you using - I don't think the OpenAI models have native PDF Support do they? I added this for the Anthropic endpoint a couple of months ago.

Hi @LucaButBoring -- this is a great initiative and content. Not sure if you are aware of the [Community Working Groups](https://github.com/modelcontextprotocol-community/working-groups/tree/main/wg)? - there is currently an Agent Comms group where...

hi @jakemac53 -- the ListResourcesRequest and ListResourcesResult do support pagination, which is what we'd expect for navigating large lists. ReadResourceResult returns a single Resource - which may consist of multiple...

Hey there, would you mind resolving the merge conflicts and making sure the list remains alphabetical :) best, @evalstate

> Actually, on the topic of SDKs doing this transparently, should we also have an optional size parameter in the resource object, representing the byte size of the underlying resource?...