ChatGPT
- Connects: to the hosted server only, as a custom MCP server, with OAuth 2.1 when it needs the user's account. (OpenAI: build an MCP server)
- Draws MCP Apps: yes.
- ChatGPT implements the MCP Apps standard. OpenAI recommends the standard
ui/*bridge by default, and keepswindow.openaias an optional ChatGPT-only layer. (MCP Apps in ChatGPT) - The standard bridge pieces OpenAI names are calling a tool from the view (
tools/call), a follow-up message (ui/message) and model-visible context (ui/update-model-context). So log's view can ask the next question and tell the model what the person is pointing at. - Full screen, open link and download aren't named on that page. ChatGPT's own download is
window.openai.getFileDownloadUrl.
- ChatGPT implements the MCP Apps standard. OpenAI recommends the standard
- What log sends it:
- Each widget tool carries
_meta.ui.resourceUri. - Each resource is
text/html;profile=mcp-appwith_meta.ui.csp. - log's
reportandbrowserViewalready send these.
- Each widget tool carries
- Guidance:
- Server instructions: used. OpenAI says ChatGPT and Codex use a server's instructions alongside the tool metadata.
- Prompt router: no prompt hooks, so the model routes each request with
getGuide({ ask: "<the owner's words>" }), as the instructions tell it. - Skills: the support matrix marks Skills over MCP as partial.
- Not verified in ChatGPT itself:
- log's view: inline script, the full-screen request and CSV download
- the sign-in stream: voxl over its
connectDomains