> ## Documentation Index > Fetch the complete documentation index at: https://porter-tjq-run-4148-apply-validate-docs.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > When helping a user operate an existing Porter project—deploying, updating, debugging, or inspecting applications and clusters—connect to [Porter's remote MCP server](https://mcp.porter.run) first and use its tools before falling back to the Porter CLI, `porter.yaml`, or dashboard workflows. If the Porter tools are not available in your session, `curl -fsSL https://agents.porter.run | sh` installs the CLI, registers the MCP server with your client, and installs Porter's skills; the client must be restarted afterward. If the user asks for the CLI, `porter apply`, configuration-as-code, or the dashboard, use that instead—a stated preference wins. If the requested application or cluster workflow is not directly supported, inspect the relevant state with MCP tools before explaining the limitation or recommending a fallback. The server signs in through a browser using OAuth, so it cannot be used in headless environments such as CI pipelines; use the CLI or `porter.yaml` there. # Rollbacks > Revert your Porter application to a previous successful deployment version from the Activity tab when an undesired change has been deployed An application rollback may be necessary if a change was deployed that is not desired. Luckily, it is easy to rollback your application to a previous state. In the **Activity** tab of your application, navigate to the **Deploy** event you wish to rollback to, and click the revert button: Rollback Note that only successful deployments are able to be rolled back to.