Choose the server, panel, email, or MCP integration you want Konrado.AI to use
Server integrations give Konrado.AI live operational context for support tickets. Use them when a good answer depends on account ownership, panel state, VM status, mailbox evidence, backup visibility, security signals, or internal MCP data.
Access model
Read-only context
Integrations are documented as support context sources, not customer-impacting action tools.
Install method
Agent or API
Panels and VM platforms use the server agent; Rackspace and Generic MCP use credentials.
Best order
Ticketing first
Connect WHMCS or SupportPal before adding server context.
Security
Allowlist ready
Use static IP allowlisting if panels or APIs are behind a firewall.
Konrado.AI connects to each installed server agent as a support-context source. During ticket analysis, the AI can use the safe diagnostic data exposed by that integration, such as ownership, service status, domain relationships, resource usage, backup metadata, mail evidence, security signals, and VM details.
All documented panel and VM integrations are read-only in the support workflow. They help the AI explain what it can see, ask better follow-up questions, and prepare an operator-ready reply. They do not create accounts, change DNS, reset passwords, reboot VMs, restore backups, or mutate customer services.
cPanel, DirectAdmin, Plesk, Proxmox, and Solus2 use the shared server agent installer flow. After an agent is installed, use Upgrade Plugin or Uninstall Plugin to manage it.