MCP Apps:interface in ChatGPT and Claude
Updated · 4 min read
An MCP server's tool can return more than text: an interactive view such as a product card, a chart, a form or a cart. Since January 2026 there's one open standard for it, MCP Apps, supported by ChatGPT, Claude and several other apps. Here is how it works and what to know before you start.
What MCP Apps is
MCP Apps is the first official extension of the MCP protocol. It grew out of the MCP-UI project and OpenAI's Apps SDK, with OpenAI and Anthropic working on it together. The stable version of the specification is dated January 26, 2026.
Views work in Claude (in the browser, the desktop app, Cowork and on mobile), in ChatGPT, in Visual Studio Code with GitHub Copilot, in Microsoft 365 Copilot, in Goose and in Postman. Claude calls them interactive connectors, and they're on by default. On Team and Enterprise plans an Owner can turn them off.
How it works
- A view is an HTML resource with a ui:// address and the text/html;profile=mcp-app type.
- A tool points to its view in the _meta.ui.resourceUri field. When the model calls it, the app shows the view and passes it the tool's input and result.
- The view runs in a sandboxed iframe and talks to the app over postMessage in JSON-RPC. It can call another tool, send a message to the chat, add information to the model's context, open a link or ask for full screen.
- Three display modes: inline in the conversation, full screen and picture-in-picture.
- The app passes on its theme (light or dark), CSS variables, fonts and language, so the view looks like part of the conversation.
- External domains (APIs, images, fonts) have to be declared in _meta.ui.csp. Anything else won't load.
ChatGPT
- ChatGPT supports the MCP Apps standard. OpenAI now recommends the older window.openai API only for features the standard doesn't have, and the old field names still work.
- ChatGPT only: checkout (requestCheckout), file upload and selection, modals and saved view state.
- Four forms: an inline card, a card carousel, full screen and picture-in-picture.
- For a Plugin Directory submission, a plugin with UI needs a unique domain in _meta.ui.domain and an exact list of domains in its CSP. Embedded frames from other domains (frameDomains) have to be justified.
Claude
- Claude derives the view's domain from the server URL itself (a subdomain of claudemcpcontent.com). That doesn't work for local stdio servers.
- On mobile the view runs in a native WebView, without camera, microphone or location. Frames from other domains are restricted for now.
- A tool result above about 150,000 characters breaks the view, and a call times out after 240 seconds.
- For the Connectors Directory you need 3–5 PNG screenshots at least 1000 px wide, each with its prompt. The full list of requirements is in our submission guide.
SDK and testing
The official @modelcontextprotocol/ext-apps package has a server part (registerAppTool, registerAppResource), a view part (App.connect) and React hooks. The repository has templates for React, Vue, Svelte, Preact, Solid and plain JavaScript, plus a migration guide from the Apps SDK.
You can check a view in the Apps tab of the MCP Inspector, and the --app-info flag shows the declared CSP, permissions and domain. Then test it in the real apps, as described in How to test an MCP server.
View or text?
A view makes sense when something is easier to show or click than to describe:
- Comparing products, a chart, a map, a design preview.
- A form with many options, such as configuring an order.
- A multi-step process or data that changes live.
Design rules
- An inline card: at most 2 buttons and 4–5 pieces of information, no scrolling inside and no dropdown menus. A carousel: 3–8 items.
- Colors and fonts from the app's theme, with dark mode support.
- Separate tools for data and for display. Attach the view only to the latter.
- The tool returns the full data in structuredContent, so it works without the view too and the model knows what the user sees.
- Pass the user's choice in the view (a selected product, say) to the model through ui/update-model-context.
- Will one view work in ChatGPT and Claude?
- Yes, if it uses the MCP Apps standard. ChatGPT-only features such as checkout or file uploads have to be replaced or hidden in Claude.
- I have an app on the old Apps SDK. Do I have to rewrite it?
- Not right away: ChatGPT still supports the old field names and window.openai. Moving to MCP Apps pays off when the same plugin should work in Claude or VS Code. The ext-apps repository has a migration guide.
- Can the view fetch data from my API?
- Yes, if the API's domain is declared in the CSP. Often it's better to call an MCP server tool from the view, though, because sign-in and permissions then stay on the server.
- MCP integration: your ERP, store and CRM in ChatGPT and Claude
- Aesthetic clinic websites in Poland
- Online booking for a private clinic
- An AI assistant for your clinic: what's allowed in 2026
- ChatGPT product feed: get your products into ChatGPT shopping
- Clinic advertising in Poland: what a website may say
- Your clinic in ChatGPT and Google
- Patients from abroad: a medical tourism website
- Claude connectors: what they are and how to add one
- MCP servers in ChatGPT: how to connect one
- How to connect WooCommerce to ChatGPT in 2026
- OAuth for MCP servers: sign-in in ChatGPT and Claude
- MCP server security: what to check before launch
- How to test an MCP server in ChatGPT and Claude
- MCP server or API? When you need both
- Hiring a software studio in Poland
- Your Shopify or WooCommerce store in ChatGPT
- What is an MCP server? Explained for online stores
- Claude connector for SaaS: what it takes
- How to sell in ChatGPT in 2026
- MCP server, ChatGPT plugin or Claude connector?
- How to get listed in ChatGPT and Claude
Want an interface inside ChatGPT and Claude?
ChatGPT plugins