Skip to main content
Listing changes and app changes follow different paths. Use the smallest one that matches what you changed.

​
Change the listing

Use the developer dashboard or MCP app_update to edit the public name, summary, or description. These updates do not change the hosted App ID, public handle, or an existing revision.

​
Change how the app works

Source, assets, settings, and behavior belong in a new immutable revision. Make the changes locally, then test and submit them:
The previous revision stays intact with its preview and review decision. This makes it clear which version was evaluated and which version people receive.

​
Protect existing installations

Treat removed settings, changed field IDs, new required credentials, or a different data provider as a migration. Keep useful defaults for existing installations and explain any action people need to take in the release notes.
Do not reuse a credential or OAuth connection for a new purpose without telling the user. Add a new field or request authorization again, then complete the required policy review.
Last modified on September 2, 2026