Future of ChatGPT Apps SDK with MCP Apps Standardization?

ChatGPT Apps SDK
1

With the announcement of MCP Apps as an official MCP extension (now supported by Claude,
ChatGPT, Goose, and VS Code), I’m curious about the future direction of the ChatGPT Apps
SDK.

The blog post mentions:
“MCP Apps builds upon the foundations of MCP-UI and the ChatGPT Apps SDK”

And Nick Cooper is quoted saying OpenAI is “proud to support this new open standard.”

For those of us currently building with @openai/apps-sdk, I have a few questions:

  1. API Unification: Will the ChatGPT Apps SDK eventually align with the
    @modelcontextprotocol/ext-apps API? The current APIs are similar but not identical (e.g.,
    useToolOutput() vs app.ontoolresult).
  2. Migration Path: Should we start building new apps with @modelcontextprotocol/ext-apps
    instead of @openai/apps-sdk? Or will ChatGPT continue to support the current SDK
    indefinitely?
  3. Feature Parity: Will features like useWidgetState() and setWidgetState() be available in
    the MCP Apps standard?

Basically: what’s the recommended path forward for developers who want to build apps that
work across both ChatGPT and Claude?

Thanks!

13 Likes
2

Found the answer, we have to migrate:

2 Likes