From ac65f4602636d3a88d7917e6b6b0e233554911f5 Mon Sep 17 00:00:00 2001 From: Olivier Chafik Date: Fri, 23 Jan 2026 13:01:45 +0000 Subject: [PATCH] spec: remove Intents reference from rationale (#187) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Update spec: drop Intents reference, rename Notify to Log - 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 * spec: remove Intents reference from rationale Remove 'intent' from the list of MCP-UI message types - Intents concept was dropped in earlier discussions. --------- Co-authored-by: Claude Opus 4.5 --- specification/draft/apps.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/draft/apps.mdx b/specification/draft/apps.mdx index 7401824..25d84e6 100644 --- a/specification/draft/apps.mdx +++ b/specification/draft/apps.mdx @@ -1540,7 +1540,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