What
- A new protocol subtype
mcp_read_resourcelets a host read aui://resource from a connected MCP server (viaresources/read) for rendering an MCP Apps UI panel. - Tool definitions can now carry a validated
_metafield surfacingui.resourceUriandui.visibility(or the deprecated flatui/resourceUri). - Two new capabilities,
mcp_read_resource_v1andmcp_tool_ui_meta_v1, are advertised during session setup, unless disabled by a local flag.
Why This is the initial support for MCP Apps (SEP-1865), letting MCP servers define rich UI panels tied to their tools rather than plain text output.
Names in the bundlemcp_read_resource_meta.ui
Documented inclaude-code/agent-sdk/typescript
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up _meta.ui, on Design guidelines.
Set `_meta.ui.prefersBorder` to `true` or `false` to control whether your content renders with a border. If you don't set it, content renders borderless on web and bordered on mobile.connectors/building/mcp-apps/design-guidelines see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up _meta.ui, on Design guidelines.