Hi everyone, I have a couple of questions during development regarding whether I need to resubmit my ChatGPT App:
Scenario 1: Backend Optimization Only (No Changes to MCP Server)
I’ve made some performance optimizations to my backend (e.g., improved processing speed and response efficiency), but there are no changes to the MCP Server itself. The MCP Server information in the ChatGPT App application page also remains exactly the same.
In this case:
Do I need to resubmit my ChatGPT App?
Or can I continue using the existing setup without any additional action?
Scenario 2: Minor Schema / Widget Updates (No Changes to MCP Server)
In another scenario:
The MCP Server remains unchanged, but I’ve made some minor updates to:
My question is:
For these kinds of changes (not at the MCP Server level), do I need to resubmit the ChatGPT App?
Or as long as the MCP Server is unchanged, no re-approval is required?
Have the same question here.
Hey folks, good question, that part can feel a bit unclear.
Even for backend-only tweaks or small schema or widget updates, it’s still treated as ongoing maintenance. Once your app is published, that version is locked.
So to make changes, you’ll need to:
- Create a new draft version of your existing app (not a new app)
- Resubmit it for review
Each resubmission starts a new review cycle. It helps a lot to clearly list what changed in the release notes so reviewers can quickly understand the update.
You can find more details here: Submit and maintain your app.
-Mark G.
So, could you confirm what happens if a new parameter is added to a tool or the description is changed? Does ChatGPT read these updates and it is aware of them so it refreshes the tool information? Or it uses the data that it already has until a new app review is submitted?
@casey-chow @OpenAI_Support apologies for tagging directly but this is quite important to us.
We updated one of our MCP apps (which has already been approved to the ChatGPT App Store) to use Streamable HTTP rather than SSE as that is what is recommended for MCP apps now. We want to resubmit the new version and get it published. But we are afraid that pushing to our main branch and resubmitting will break our live version.
Can you confirm what happens in this scenario? If a team changes backend or internal plumbing and pushes to their main branch, would that break their live published app or something?
We want to move ASAP but after testing with ChatGPT locally it seems you guys cache or lock the type of transport and other things, which makes us think our app will likely break on the directory and to the public.
Please help with this. Creating a new MCP deployment based on another branch and pointing to another URL in order to resubmit that seems like an extremely wasteful process.
I’m not very certain about the SSE to Streamable HTTP behavior; my recommendation would be to support both temporarily (which is consistent with a double-write system) and wait for SSE usage to drop to an acceptable level before removing the SSE transport.
And if we support both, can we then confidently push to our main branch, trust that the live app won’t break, and also resubmit the new version?