For a VPS bought through current hosted MCP or local impreza-mcp 0.54.0 or later, omitting the app requests the Impreza Agent by default; review that choice in the order proposal. Direct portal and REST orders keep No app, and an explicit supported app choice is respected. You can also add the Agent later on an eligible VPS. A connected AI assistant can check eligibility, offer installation and follow its result. Connecting MCP alone does not install the Agent on an existing server.
Already have a server at another provider?
Use impreza_add_server through current hosted MCP or local impreza-mcp 0.53.0+ to request an installation command for a compatible external server, with deploy permission. The first external-server slot is free without a plan or balance. You still review and authorize running the command with administrator access; this is not the managed VPS installation below.
Follow connect your own server for the one-time token, account limits and domain options. Adding a machine does not copy its existing apps, and a generated installer is not proof that the Agent is online.
Check whether this path fits your server
Use an active, supported Linux Impreza VPS with a responding QEMU guest agent. A stopped server must be started first. Windows, control-panel installations, unsupported or unreadable operating systems and servers already registered with an Agent do not use this installation path.
The current automated path also refuses AlmaLinux, Rocky Linux, RHEL, CentOS and Oracle Linux. For those or a server at another provider, follow the portal’s manual installer and connect your own server. Do not interpret Agent installation as moving an external hosting contract or copying its data.
Use current hosted MCP or local impreza-mcp 0.49.0+ with manage scope and an unrestricted account credential. A credential limited to selected resources cannot run this workflow. Granting manage allows other important operations too; review the connection’s permissions before using it.
1. Ask the assistant to check the VPS
For example: “I want to deploy an app on this VPS. Check whether it needs the Impreza Agent and whether the automated installation is available. Ask me before installing anything.”
The assistant can inspect agentless servers in account overview and use impreza_get_agent_install for a specific server. If eligibility is unavailable or not_checked, ask it to check that server rather than assume it is ready. Read the reason for a refusal and choose the supported alternative.
2. Review the proposal before approving
The first impreza_install_agent call installs nothing. It returns the proposal and a confirmation token bound to that server, credential and exact installer script, valid for five minutes. Review what will run and explicitly agree before the assistant makes the second call with that token.
The installation runs with administrator privileges inside the VPS, installs Docker if needed and the Agent service, and registers the server with your account. It is a real server change. If your human-approval policy covers the security class, the operation waits for your decision in the client area.
3. Follow the result
Ask the assistant to poll impreza_get_agent_install. Wait for online, then confirm the server in My Apps before starting an app deployment. An accepted install request is not an online Agent. If the proposal expires, prepare and review a new one; do not reuse an old consent token.
Prefer the portal button?
Open the VPS service and choose Install the Impreza Agent with one click. The card presents the script and its SHA-256, with explicit administrator consent. It uses the same eligibility checks and installs one Agent at a time.
Check the version before important operations
The published stable Agent is 0.6.43, checked on 29 October 2026, for Linux amd64 and arm64. New installations use the supported installer; an existing server keeps its installed version until you request an update. Finish active operations before updating. The updater verifies the offered artifact’s size, hash and embedded version before changing the installed Agent’s startup configuration. A refused update leaves that configuration unchanged. After an update, verify the Agent’s online report and your apps separately. See the 0.6.43 release notes for the routing and recovery changes.
The current stable release includes the security and domain-change improvements introduced in 0.6.39: an updated Go runtime with TLS and HTTP security fixes, and a proxy reload before a successful domain change is marked complete, including an interrupted change that is retried. 0.6.40 corrected the optional disk-encryption status report and bound it to the Agent’s own identity. 0.6.41 adds the local control used to enable that report for the same server and includes checks for supported encryption preparation. Updating the Agent alone does not encrypt a disk or authorize a host change.
The earlier 0.6.37 improvements remain: an onion service is ready only after Tor confirms publication, and staging clones preserve an app’s fixed runtime user. Check the installed version, available capabilities and each operation’s result; installing the Agent is not proof that an app or its public route works. Read Agent updates for the signed update workflow.
Choose disk encryption separately from Agent installation
The Ubuntu 24.04 (encrypted disk) image is now offered when ordering or reinstalling a supported Impreza VPS. It prepares the environment for you to encrypt the root disk with a passphrase that Impreza neither receives nor stores. Selecting the image or updating the Agent does not perform the encryption: you prepare it on the server and set the passphrase through the documented SSH unlock flow.
Keep the passphrase outside AI chat and the provider’s web console. After every boot you unlock the disk yourself; Impreza has no recovery key. The Agent reports the state only after you enable reporting locally. The encryption itself does not depend on that report. Follow encrypted-disk setup and limits before choosing this option.
Check installation again after an OS reinstall
Once an OS reinstall has completed, ask the assistant to check that VPS again with impreza_get_agent_install, or open its service page. The current eligibility result determines whether a fresh Agent installation is available; an old offline record is not proof that an Agent is still running. If an installation is already in progress, follow that request instead of starting another.
Review a fresh proposal and authorize it only if needed. Wait for a current online report afterward. Reinstalling the Agent does not restore your apps, databases or onion identity; use your separate recovery plan for those.
Keep the installation optional
Adding the Agent does not change the software choice on the original order. Reinstalling the OS does not automatically put it back. Use Uninstall agent in My Apps when you want to remove it. Updating the MCP package and updating an existing Agent are separate actions.
Next, deploy a supported app and check its result. Use private secret entry when a supported runtime variable needs a password or token. The technical Agent installation reference lists current refusal reasons and REST operations.