Jonathan Hefner

This is an alternative to [SEP-1700](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1700), based on various feedback. Notably, it omits the redirect. I still think the redirect (to a unique URL) is valuable for routing and idempotency...

> > POST a JSON array of its buffered responses > > Is this a new RPC? We don't have batching any more. Not a new RPC, but also not...

> > > > POST a JSON array of its buffered responses > > > > Not a new RPC, but also not batching. Batching is a _data-layer_ concept for...

> My reading of this is that if the Client looses the buffer contents for some reason before receiving the HTTP 204 there's no way for it to obtain the...

@halter73 I'm trying a different approach in [SEP-1858](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1858) which you might find more appealing. The relevant behavior is controlled by explicit custom SSE events.

Closing this in favor of [SEP-1858](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1858). I think the redirect (to a unique URL) that this SEP proposes is still valuable for routing and idempotency purposes, but it can be...

I ran into this as well with a similar use case (I want to render React components as static HTML and do post-processing on that HTML, such as removing or...

Thank you for the pull request! Unfortunately, we currently do not have the resources to maintain translations like this. However, we are open to suggestions about how to better meet...

I think there is a use case for returning a temporary resource that can be read via `resources/read` but is not listed via `resources/list`. In which case, I think it...

@Madd0g > We're out of luck as soon as we ask ourselves "hey, maybe the image generated by this tool should only be shown to the user, not the AI?"...