{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifsc2njnzx7ut3eezl43krndlucyjec3xshtbukz3deajbjq7aynm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3ml6y2dyr2vd2"
  },
  "path": "/t/questions-about-mcp-server-changes-and-chatgpt-app-re-submission/1379394#post_5",
  "publishedAt": "2026-05-06T14:28:21.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@casey-chow",
    "@OpenAI_Support"
  ],
  "textContent": "@casey-chow @OpenAI_Support apologies for tagging directly but this is quite important to us.\n\nWe 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.\n\nCan 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?\n\nWe 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.\n\nPlease 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.",
  "title": "Questions About MCP Server Changes and ChatGPT App Re-submission"
}