docs(mcp-apps): document capability advertisement across protocols - #4061
pjmsmithgoogle wants to merge 2 commits into
Conversation
…egacy protocols Updates documentation note and capability negotiation details in docs/en/documentation/configuration/mcp-apps/_index.md: - Clarifies that modern protocol 2026-07-28 uses standard extensions capability exchange in ServerCapabilities and ClientCapabilities. - Explains that legacy protocols (2024-11-05, 2025-03-26, 2025-06-18, 2025-11-25) convey UI metadata via _meta.ui on tools in tools/list and serve UI assets via resources/read.
There was a problem hiding this comment.
Code Review
This pull request updates the MCP Apps documentation to clarify the capability negotiation and graceful degradation differences between modern and legacy protocol versions. The review feedback correctly identifies that the modern protocol transmits client capabilities dynamically within the '_meta' object under 'io.modelcontextprotocol/clientCapabilities' rather than using a root-level 'capabilities' object, and provides a corrected JSON example to ensure accuracy.
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request updates the MCP Apps documentation to clarify protocol version differences and capability negotiation. Specifically, it details how the modern protocol (2026-07-28) utilizes dynamic client capability negotiation via request metadata, whereas legacy protocols directly expose UI metadata on tools and serve templates via resources. No review comments were provided, so there is no additional feedback to address.
Description
Updates documentation note and capability negotiation details in docs/en/documentation/configuration/mcp-apps/_index.md:
PR Checklist
CONTRIBUTING.md
bug/issue
before writing your code! That way we can discuss the change, evaluate
designs, and agree on the general idea
review
!if this involve a breaking change🛠️ Fixes #4055