After the order: how an AI agent runs its own VPS over MCP

说明与用途

代理通过MCP自动化管理VPS生命周期，包括状态、指标、功率、计划变更、余额续费和支持工单，但破坏性操作和余额充值需要人工确认。

问题

An AI agent must manage a VPS after ordering it, handling SSH readiness, monitoring metrics, renewing balance, and escalating issues.

结果

The agent can autonomously manage most VPS lifecycle tasks via MCP, but destructive actions and balance funding still require human intervention.

工作流

• Order VPS via order_vps
• Poll get_vps_status until status is active and access.ssh_ready is true
• If no SSH key, call reveal_password after boot
• Monitor metrics with get_vps_metrics daily
• Use power_vps to start/stop/reboot as needed
• Rename with set_hostname
• Renew balance by checking get_balance and topup_balance when low
• Pay invoices with pay_invoice after top-up
• Handle plan changes with get_upgrade_options and change_plan
• Escalate issues with create_ticket and reply_ticket
• Delegate service to a human operator with delegate_service

证据

order_vps returns as soon as the order is paid from the balance. The server is created in the background, usually in about a minute.

来源

A well-behaved agent waits for access.ssh_ready instead of hammering port 22.

来源

If the order had no SSH key, the root password is waiting. reveal_password hands it over exactly once, and only after the VM has finished booting.

来源

get_vps_metrics returns CPU, memory, network and disk as time series for the last hour, day, week or month.

来源

power_vps does start, stop and reboot. One detail from testing: if the server isn't active, the tool returns a 409 with a hint to check the status first.

来源

When the balance is low, topup_balance produces a crypto checkout link: USDT, USDC or ETH on Base, Ethereum or Polygon.

来源

Destructive actions are deliberately awkward. reinstall_vps and an immediate cancel_service both require the server's exact hostname as confirm, and their descriptions tell the agent to check with a human before calling.

来源