From 004635a41f3c91393d76c0c06d5a42a2e8036e82 Mon Sep 17 00:00:00 2001 From: ochafik Date: Sat, 20 Dec 2025 03:11:07 +0000 Subject: [PATCH] Update spec: drop Intents reference, rename Notify to Log MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Remove "intent" from the list of MCP-UI message types in the rationale section (Intents concept is being dropped) - Rename "Notify" to "Log" in the lifecycle diagram to better reflect that notifications/message is for debugging/telemetry logging, not for sending messages to the chat (which is now ui/message) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- specification/draft/apps.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/specification/draft/apps.mdx b/specification/draft/apps.mdx index 6e33f813..66dc5b88 100644 --- a/specification/draft/apps.mdx +++ b/specification/draft/apps.mdx @@ -1032,9 +1032,9 @@ sequenceDiagram else Message UI ->> H: ui/message H -->> H: Process message and follow up - else Notify + else Log UI ->> H: notifications/message - H ->> H: Process notification and store in context + H ->> H: Log message (for debugging/telemetry) else Resource read UI ->> H: resources/read H ->> S: resources/read @@ -1293,7 +1293,7 @@ This proposal synthesizes feedback from the UI CWG and MCP-UI community, host im **Alternatives considered:** -- **Custom message protocol:** Current MCP-UI approach with message types like tool, intent, prompt, etc. These message types can be translated to a subset of the proposed JSON-RPC messages. +- **Custom message protocol:** Current MCP-UI approach with message types like tool, prompt, etc. These message types can be translated to a subset of the proposed JSON-RPC messages. - **Global API object:** Rejected because it requires host-specific injection and doesn't work with external iframe sources. Syntactic sugar may still be added on the server/UI side. #### 3. Support Raw HTML Content Type