For Confluence administrators maintaining the installed app.
Upgrade
-
Choose the package for your target Confluence major version and review Compatibility and limitations. A move from Confluence 9 to 10 also requires the Confluence 10 app package.
-
Install the updated package through Manage apps. Where UPM requires a signature, use the signature supplied for that exact package.
-
Confirm the app is enabled and shows the expected version. Review MCP space policy before reconnecting clients.
Saved policy takes precedence over legacy JVM properties. Do not assume a restart, uninstall or reinstall resets it. See Install and configure | Existing JVM configuration for policy precedence and legacy migration. Before a downgrade, confirm that the target package supports your policy configuration and required tools.
Uninstall
In Manage apps, select the app and choose Uninstall. Its MCP endpoint becomes unavailable. Pages created or updated through MCP remain in Confluence; uninstalling does not reverse their edits or permissions.
Revoke client tokens that are no longer needed. Treat policy cleanup separately; uninstalling is not a documented policy reset. For problems, see Troubleshooting.
Extended tool availability
After upgrading, reconnect or refresh the client’s tool discovery and check the installed build’s advertised operations. A downgrade can remove extended tools; it does not undo comments, labels, attachments or page history created through native Confluence. Use the existing native content-change and recovery processes, and retain the intended administrator policy.