{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieq3bfft5scij2a2puiex2qgv5erpxwsc4ykxpqylavghj4xxzleq",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mfs2xgwey462"
  },
  "path": "/t/mcp-apps-ui-notifications-tool-result-missing-meta-in-chatgpt/1375226#post_1",
  "publishedAt": "2026-02-26T19:36:00.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "mcp apps spec"
  ],
  "textContent": "I’m migrating a ChatGPT app UI from the OpenAI bridge (window.openai) to the MCP Apps bridge (ui/* over postMessage).\n\nIn the OpenAI bridge, we relied on window.openai.toolResponseMetadata for UI-only data and it worked.\n\nAfter moving to MCP Apps, we expect the same data to be available as top-level params._meta in ui/notifications/tool-result (per docs/spec), but it is missing in ChatGPT.\nmcp apps spec\n\n### Expected\n\napp.ontoolresult should receive:\n\n  * params.content\n\n  * params.structuredContent\n\n  * params._meta (UI-only metadata)\n\n\n\n\n### Actual (ChatGPT host)\n\napp.ontoolresult receives:\n\n  * params.content\n\n  * params.structuredContent\n\n  * params._meta\n\n\n\n\nSo the tool-result notification arrives, but top-level _meta does not appear to be forwarded.",
  "title": "MCP Apps: ui/notifications/tool-result missing _meta in ChatGPT"
}