{"version":"2.1.317","anchor":"mcp-app-view-state-readable-via-readwidgetcontext-tool","canonical_anchor":"mcp-app-view-state-readable-via-readwidgetcontext-tool","heading":"Claude can read what an MCP App view has shared","tier":"notice","area":"MCP Apps","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/mcp-app-view-state-readable-via-readwidgetcontext-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Claude can read what an MCP App view has shared\n\nA new `ReadWidgetContext` tool lets Claude read the latest state that an MCP App view has shared with Claude Code\n\n**Unclear.** Whether the ReadWidgetContext tool is available by default, or only when something switches it on, is not shown.\n\n**What**\n\nAn MCP server is an outside service that gives Claude extra tools. Some of them provide an MCP App, which shows you an interactive view. A new tool, `ReadWidgetContext`, lets Claude read the latest state such a view has sent to Claude Code, in other words what the view has shared.\n\n- Each view is identified by the ID of the tool call that opened it. A tool call is one use of a tool by Claude. An app opened outside a tool call is identified by its thread instead.\n\n- A reminder next to your message lists the IDs of the views whose shared state Claude Code is holding.\n\n- The state Claude reads is marked as untrusted data, not as instructions to follow.\n\nFor programs built on Claude Code, user prompts now also carry `widgetViews` and `widgetViewsMore` fields.\n\n**Why**\n\nClaude can now take into account what you did inside an MCP App view. Because that state is treated as data rather than instructions, a view cannot use it to tell Claude what to do.\n\n- Area: MCP Apps\n- Tier: You'll notice\n- Useful: 5\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}