You do not need to click through a dashboard to get a server online anymore. With the Impreza MCP, your AI coding assistant can create the account, place the order, provision the machine and deploy your app, all from the chat. This guide shows the whole flow.
What you need
- An available Impreza integration in your AI assistant, or a compatible MCP client. The connection paths differ; review the tools and permissions offered by yours
- An account with no KYC and no email required; funding and provisioning times vary
- A crypto wallet to fund your balance
The steps
Connect the Impreza MCP
For ChatGPT, open the Impreza Host plugin. In Claude, look for Impreza MCP among its community integrations; this is distinct from the Claude Code setup below. Follow the authorization offered by that integration and start with a read-only inventory.
For a compatible client with custom remote MCP support, use the remote connector: add https://mcp.imprezahost.com/mcp in your AI client and click Authorize. No install, no API key. See connect your AI agent with OAuth.
Prefer the local server, or need to upload the folder you are working in? Install it with one command:
npx -y impreza-mcp setup --tool claude-code
Swap the tool name for the one you use, such as cursor, continue, zed or codex-cli.
Create your account by chat
Ask the agent to create a fresh account without supplying a personal email address. Save your Account ID and one-time recovery code securely. Use your Account ID and password for portal login; the recovery code is for resetting a lost password. See signup without email for the complete flow.
Top up in crypto
Tell the agent how much to add. It can create a top-up invoice in BTC, XMR, USDT-TRC20 or TRX and return the payment details. Pay from your wallet using the currency and network shown on the invoice. Wait for confirmation and check the credited balance before ordering; creating an invoice does not fund the account. See crypto balance top-ups.
Order and deploy
For the configurable VPS, ask the assistant to show available locations, operating systems, vCPU, memory, disk, billing cycles and initial apps. Choose a configuration and review its exact amount due today, renewal price and location availability before confirming. A quote does not reserve capacity or place an order. The WordPress VPS cards lead to the same configurable product; you can still change the country, hardware, OS and app in checkout.
The MCP purchase flow presents the configuration and a confirmation step before ordering. A client using external checkout receives a prefilled store link to review and complete there. Current hosted MCP and local impreza-mcp 0.54.0 or later request the Impreza Agent when the app is omitted, and show the choice for review. Direct portal and REST orders keep No app; an explicit supported app choice is respected. Review the initial app before confirming, or add the Agent later on an eligible VPS. Wait for provisioning and confirm that the Agent is online; an accepted order or OAuth connection alone does not mean the server is ready. See the VPS order reference for supported choices and current MCP version.
Next, choose a supported catalog app or a compatible Docker or Git project. Review the deployment configuration, start it, and check the resulting app URL and logs. Configure auto-deploy on Git push separately if needed, and verify each deployment result.
Store the one-time recovery code in a password manager before you move on. Keep it separate from routine prompts and delegated credentials. It is a recovery secret, not your everyday login password.
No-email signup reduces the personal information you provide at registration. It does not mean there are no account or operational records, or that payments are untraceable. Check the account privacy report guide for its scope and limits, and review the service policies for your chosen product.
Continue with visual controls in the chat
On an AI client that supports MCP Apps, the hosted connector and local impreza-mcp 0.55.1 can show a VPS status card, a catalog deploy wizard and a BTC/XMR top-up payment card with QR. These keep the account’s permissions and confirmations; a visible card does not itself install an Agent, fund the account or approve a purchase. Use the linked steps for each task.
Add the Agent to a VPS you already ordered
On an eligible Impreza VPS ordered with No app, open the service page and choose Install the Impreza Agent with one click. Review the installation script, its hash and the administrator consent before continuing. Confirm that the Agent becomes online before deploying an app. The button depends on the supported OS, guest-agent access and service state; Windows and control-panel installations do not use this path.
A connected AI assistant can offer the same installation for an eligible Impreza VPS. Ask it to check the server first, review the proposed installer, and explicitly agree before it runs. The request needs manage permission; a restricted credential cannot use this install path, and a configured human-approval policy may require a decision in the portal. Follow install the Agent with your AI assistant for the two-call flow and eligibility checks. Package updates and server Agent installation are separate actions.
When an app later needs a password or token, enter it outside the chat. Connecting MCP does not make secret values safe to paste into a conversation.
For a machine at another provider, follow Bring your own server and run the portal-generated command on the server you administer. The AI connection, server installation and app deployment are separate steps.
Keep the project understandable
Use My Apps → Projects and environments to group existing apps and inspect deployment results, previews, primary domains and backup policy. Opening a project does not deploy anything or copy production data. An assistant can help read the same supported resources within the access you grant. See the project and environment documentation.
After your first deploy
Use app inspection and maintenance to check a supported deployment. Before important changes, review app backups to Impreza S3 and test recovery for your app. These backups are separate from whole-VPS backups. If an assistant only needs a limited task, review delegated app access instead of sharing broad credentials.
Prepare recovery for a supported app
For a running Memos 0.31.0 or Uptime Kuma 2.5.5 app, Protect this app in My Apps helps create and test a cold standby in another reported country. The hosted connector and local impreza-mcp 0.50.0+ provide the impreza_protect_app playbook for the same steps. You approve creation, pairing and the first drill separately; the assistant does not buy servers or switch traffic. Follow the failover guide for eligibility and recovery limits.
Get started
Read the full documentation at docs.imprezahost.com, then spin up an offshore VPS or an offshore dedicated server. Already have a compatible VPS or dedicated server elsewhere? Connect your own server to Impreza instead of ordering another machine; adding the Agent is separate from migrating existing applications.