docs(protocol): define MCP transport binding for A2UI and align MCP s…#627
docs(protocol): define MCP transport binding for A2UI and align MCP s…#627iamrajhans wants to merge 1 commit intogoogle:mainfrom
Conversation
…ample payload to messages[]
iamrajhans
requested review from
dmandar,
gspencergoog,
jacobsimionato and
zeroasterisk
as code owners
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request formalizes the A2UI-over-MCP transport binding and aligns the sample server implementation. The documentation additions in a2ui_protocol.md for both v0.9 and v0.10 are clear, detailed, and well-structured. The corresponding changes in the Python sample server correctly reflect the spec by using a messages key and introducing a constant for it, which improves code quality. My only feedback is a minor suggestion to improve link consistency in the markdown files.
| - For server-to-client UI updates, `messages` MUST validate against [server_to_client_list.json](../json/server_to_client_list.json). | ||
| - For client-to-server events, `messages` MUST validate against [client_to_server_list.json](../json/client_to_server_list.json). |
There was a problem hiding this comment.
For consistency with other schema links in this document (like [a2ui_client_capabilities.json]), it would be better to use reference-style links here. This would make all schema links follow the same pattern.
Here is the suggested change:
- For server-to-client UI updates, `messages` MUST validate against [`server_to_client_list.json`].
- For client-to-server events, `messages` MUST validate against [`client_to_server_list.json`].You'll also need to add the corresponding definitions at the end of the file:
[`server_to_client_list.json`]: ../json/server_to_client_list.json
[`client_to_server_list.json`]: ../json/client_to_server_list.json| - For server-to-client UI updates, `messages` MUST validate against [server_to_client_list.json](../json/server_to_client_list.json). | ||
| - For client-to-server events, `messages` MUST validate against [client_to_server_list.json](../json/client_to_server_list.json). |
There was a problem hiding this comment.
For consistency with other schema links in this document (like [a2ui_client_capabilities.json]), it would be better to use reference-style links here. This would make all schema links follow the same pattern.
Here is the suggested change:
- For server-to-client UI updates, `messages` MUST validate against [`server_to_client_list.json`].
- For client-to-server events, `messages` MUST validate against [`client_to_server_list.json`].You'll also need to add the corresponding definitions at the end of the file:
[`server_to_client_list.json`]: ../json/server_to_client_list.json
[`client_to_server_list.json`]: ../json/client_to_server_list.json1 participant
Summary
Formalize A2UI-over-MCP transport semantics and align the MCP demo payload shape with the spec.
Closes #558.
What changed
specification/v0_10/docs/a2ui_protocol.mdspecification/v0_9/docs/a2ui_protocol.mdmessagesarrayserver_to_client_list.json/client_to_server_list.json)a2uiClientCapabilitiessamples/agent/adk/mcp/server.pyeventstomessages.