Skip to main content
Public metadata and app source follow different paths.

​
Metadata-only change

Use the developer dashboard or MCP app_update to change the public name, summary, or description. The stable app ID and prior revisions remain intact.

​
Source or asset change

Edit the local project, then create a new revision:
Never try to replace an old uploaded revision. Immutability keeps the reviewed source, preview, decision, and digest auditable.

​
Compatibility changes

Treat schema field removal, changed identifiers, new required credentials, or a different external provider as a migration. Preserve defaults for existing installations and explain any user action in release notes.
Do not silently change what a credential or OAuth grant is used for. New purposes require a new field or renewed authorization and policy review.