The ext-apps draft spec is not currently compliant with the newer Extensions SEP-2133. It's still targeting the older SEP-1724.
I believe the biggest discrepancy right now is in the negotiation. the newer SEP says that negotiation should happen over the official MCP wire and each extension should have its own settings. (https://modelcontextprotocol.io/seps/2133-extensions#negotiation)
So instead of having a separate appInfo and hostInfo it should be in clientInfo and serverInfo respectively and negotiated via a regular initialize. Because of this, would we need to rehandle the current ui/initialize handshake to just be a readiness barrier for the iframe?
This also seems like a bigger breaking change across the board
The ext-apps draft spec is not currently compliant with the newer Extensions SEP-2133. It's still targeting the older SEP-1724.
I believe the biggest discrepancy right now is in the negotiation. the newer SEP says that negotiation should happen over the official MCP wire and each extension should have its own settings. (https://modelcontextprotocol.io/seps/2133-extensions#negotiation)
So instead of having a separate appInfo and hostInfo it should be in clientInfo and serverInfo respectively and negotiated via a regular initialize. Because of this, would we need to rehandle the current ui/initialize handshake to just be a readiness barrier for the iframe?
This also seems like a bigger breaking change across the board