Your AI assistant can help configure and operate applications without asking you to paste their supported secret variables into chat. Impreza MCP prepares an entry link; you open it in your account, enter the value yourself, and let the assistant continue after it sees a stored status.
Give the AI a task, keep the value with you
The assistant receives the application identifier, variable name and session status. The value and its hash are not returned through this workflow. A one-use link expires after ten minutes and requires the same account’s owner to sign in. It is available in the portal, hosted MCP and local impreza-mcp 0.49.0 or later.
Use this for supported runtime variables such as a custom application’s API token. When MCP recognizes a newly supplied secret, it directs you to an authenticated entry route instead of forwarding that value. Ask for the route before entering a value: a refusal cannot erase a secret already sent to an AI provider.
A private step inside your deployment workflow
- Ask the assistant to prepare secret entry for an existing app or project variable.
- Sign in to the portal, verify the target and enter the value yourself.
- Let the assistant check the stored status, review the redeploy and verify the app afterward.
The app may still use the secret at runtime. Supported redeploy, webhook and configuration flows retain stored secret references; configuration exports describe those references rather than exposing the value. The entry step does not automatically redeploy an app or prove that its connection works.
Use the portal through Tor when it fits your connection
Owner entry links support clearnet and onion access. The form loads no third-party resources. For a full Tor MCP connection, your client must support the onion endpoint and Tor transport; opening a browser page through Tor does not route the rest of your AI client’s traffic. Read MCP over Tor for the official addresses and setup.
Choose what the AI may do
Secret entry complements scoped app access and human approval for covered actions. Set permissions for the job and revoke access when it is no longer needed. A private entry form is not permission for the assistant to change everything else.
Keep a server-unlock passphrase outside the AI workflow
Supported Impreza VPS orders now offer a Ubuntu 24.04 encrypted-disk image. You prepare the encryption on the server and set the unlock passphrase yourself. The private app-variable form described above is not the place to enter that passphrase: use the separate documented SSH flow and verify the unlock host key.
Impreza neither receives nor stores the passphrase and has no recovery key. You unlock after each boot. This protects a powered-off disk; it does not protect a running, unlocked VM from the host or prevent a sufficiently privileged direct API key from authorizing destructive recovery. Read the encrypted-disk setup and permissions and delegate only the operations the assistant needs.
Know the boundary
This is not a general scanner of source code, Dockerfiles, YAML or every possible secret. Initial catalog-app credentials, private Git access, build secrets, host passwords and onion-key imports use their corresponding portal forms. Platform-generated bootstrap credentials and onion-key exports follow their existing flows. If a secret has already entered chat, rotate it.
Start with the step-by-step secret entry guide. Need a server first? Configure an offshore VPS, or connect a server you already administer.