There are two ways to connect an AI assistant to Impreza. The original one installs a local server and reads an API key and secret. The newer one is a remote connector with OAuth, and it is both simpler and safer: nothing to install, and no long-lived secret sitting on your disk.
Why OAuth is the better default
- Nothing to install. One URL added as a connector, and the client registers itself
- No API key or secret to copy, store or rotate, and no IP whitelist to maintain
- Scoped. You approve read, deploy or manage; destructive and financial actions are opt-in
- Revocable. Cut a connection off at any time from your clientarea
Connect in four steps
Add the connector
In an AI client that supports remote MCP connectors, add this as a custom connector:
https://mcp.imprezahost.com/mcp
Authorize
Click Authorize. You sign in to your Impreza clientarea and land on a consent screen. The sign-in happens on Impreza, so no credential is ever handed to the AI client.
Grant only the scopes you need
Approve read, deploy or manage deliberately. Start with the least you need; you can always connect again with more later. Destructive and financial actions have to be opted into explicitly.
Work from the chat
Your assistant can now reach the toolset your scopes allow: deploy apps and manage their lifecycle, handle domains and DNS, control VPS power, backups and reinstalls, and top up your balance in crypto.
A manage grant can power off a server, reinstall it or spend your balance. If the assistant only needs to look around, grant read. Treat destructive and financial scopes as something you turn on for a specific task, not as a default.
Every connected client is listed in your clientarea under Impreza API, in Connected Apps. Revoke anything you no longer use, and revoke immediately if a machine running an AI client is lost or compromised. Revoking is instant and does not touch your servers.
The remote connector cannot upload a project folder from your machine. If you want to deploy the code sitting in your working directory, install the local impreza-mcp server for Claude Code, Cursor, Codex CLI, Continue or Zed. Both methods work side by side. If you go that route, pair with a code instead of pasting a secret: the key is stored with restrictive permissions and never printed.
Start now
Read the setup in our documentation, then put it to work: deploy a server from your AI agent or manage DNS from the chat.