3 ms·
Sure that would be here https://modelcontextprotocol.io/docs/concepts/resources#content-changes https://modelcontextprotocol.io/docs/concepts/resources#cont...
by outlore 2y ago
Sure that would be here https://modelcontextprotocol.io/docs/concepts/resources#content-changes https://modelcontextprotocol.io/docs/concepts/resources#cont...
I think OpenAPI callback would certainly work but the client application must support this. For e.g. I don’t think ChatGPT supports callbacks (I might be wrong).
Broadly speaking I am agreed with you that OpenAPI can replicate much of the functionality of MCP, but what’s missing is the opinionated contract between client and server (similar to LSPs)
- verdverm 2y ago> opinionated contract between client and server That makes it more of a DSL on a protocol (json-rpc) than a protocol itself If you want to implement notifications without callbacks, you either (1) use an always connected session and pass messages or (2) have the client poll an endpoint