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 AI assistant that supports MCP: Claude, Cursor, Codex CLI, Continue or Zed
- 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
The quickest way is 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
Ask the assistant to show eligible plans, price and available resources before you approve the order. Select a supported server with the Impreza Agent, then wait for provisioning and confirm that the Agent is online. An accepted order or an OAuth connection alone does not mean the server is ready.
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.
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.
Get started
Read the full documentation at docs.imprezahost.com, then spin up an offshore VPS or an offshore dedicated server.