MCP Adds Native HTML UI Support, But Default Security Policy Blocks All External Requests
The Model Context Protocol has introduced MCP Apps, its first native UI extension built into the stable core spec, allowing tools to declare interactive HTML interfaces rendered inside sandboxed iframes. Developers must use the exact MIME type 'text/html;profile=mcp-app' or the host will treat the resource as a plain document with no interactive features. The platform's Content Security Policy defaults to fully blocking all external domains, meaning fetch calls or CDN script loads silently fail unless each domain is explicitly whitelisted. Communication between the host and iframe relies on hand-rolled JSON-RPC over postMessage, with no client library available yet and silent message drops for malformed requests. A browser-based validator has been released at bracketly.pages.dev to help developers check their MCP Apps configurations against the published spec before hitting these pitfalls.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in