Repository navigation
Conversation
ac13c74 to
5fd0c8d
Compare
|
The coordinated public references are now aligned to protocol revision
The primary flow uses request-scoped client capabilities, server capabilities from No second extension, custom method, or custom result type is introduced. The Inspector is pinned to ext-apps commit The references are generic and contain no product-specific example details. |
3b026c4 to
d5fe141
Compare
Add an AOT-safe host validation helper for accepted app-rendered form results, including defaults and actionable value-free errors. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: fa0e1618-463c-40d3-a1c7-2563c23e8c42
Require hierarchical ui:// resource URIs and merge elicitation into existing typed and JSON MCP Apps server capabilities without losing existing settings. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 19b7c141-8708-451b-b194-0c029b8e79a1
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
d5fe141 to
11509f2
Compare
Summary
Add app-rendered form elicitation conventions to
ModelContextProtocol.Extensions.Apps. The normative proposal is entirely contained in the MCP Apps extension: modelcontextprotocol/ext-apps#733. Core SEP-3118 is closed because no core protocol change is required.Negotiation uses the nested
elicitation: {}setting on the existingio.modelcontextprotocol/uiextension on both peers, together with coreelicitation.formand Apps MIME support.McpAppElicitation.SetAppUiIfSupportedattaches an absoluteui://resource at_meta.ui.resourceUriwithout changing the core elicitation types. Unsupported clients retain native form rendering.The request-context overload uses effective request-scoped client capabilities on
2026-07-28, with initialized-session fallback for older revisions. Metadata survivesInputRequest.ForElicitation; the host returns the App's standardElicitResultthrough the existing MRTR flow. Accepted content must match the requested schema; explicit decline/cancel results do not trigger fallback.Includes capability types, metadata and result-validation helpers, documentation, and focused tests. No separate extension package, method, result type, or core protocol change is introduced.
TypeScript reference: modelcontextprotocol/typescript-sdk#2578.
Validation
Rebased on C# SDK main
b9faee70.git diff --check: passed.