How an AI agent buys and runs its own server over MCP

EQVPS has launched an MCP-based system that allows AI agents to autonomously rent and manage virtual private servers. The agent can register an account, check plans, order a VPS, and retrieve SSH credentials without human intervention, using a prepaid balance for payments. This eliminates the need for manual signup, billing, and verification steps that previously blocked fully autonomous infrastructure provisioning.

An AI agent can write a scraper, debug it, and tell you exactly where to deploy it. Then it stops. Because the next step — actually renting the server — almost always needs a human: open an account, maybe pass an identity check, type a card number into a checkout. The agent did the hard part and now waits on you for the boring part. That gap is the whole reason this exists. We took the human out of the middle. Think about what "renting a server" really involves on a normal host. A signup form. An email to confirm. Billing details, sometimes ID. A card at checkout. A dashboard to find the IP. Every one of those assumes a person sitting there. An agent can't sit there. It can call an API, hold a token, make decisions — but it can't receive a verification email or pull out a credit card. So the moment infrastructure enters the picture, the autonomous workflow turns back into a human workflow with extra steps. You wanted an agent that ships; you got an agent that files a ticket. On EQVPS the same actions are MCP tools https://dev.to/blog/eqvps-mcp-tools-reference 16 of them plus a REST API — and crucially, the agent can get its own credentials. Here's the actual sequence: // 1. Get an account — token comes back immediately, no email, no human register account { first name: "Ada", last name: "Agent", email: "ada@example.com" } // → { token: "..." } send it as Authorization: Bearer <token from here on // 2. See what's available list plans // → plans with specs, prices, and OS image ids // 3. Make sure there's money on the balance get balance // → { balance: 25, currency: "USD" } // 4. Order — this debits the balance and provisions the box order vps { product: "nano", os id: 1, hostname: "ada-worker" } // → { service id, paid from balance: true } // 5. Read the keys to its own new server get vps status { service id } // → { ip, ssh port, password } ~60 seconds after ordering Five calls and the agent is SSH'd into a machine it rented itself. No dashboard, nobody approving each step. If you'd rather drive it from plain HTTP, the same endpoints exist over REST — MCP or REST, your call https://dev.to/blog/mcp-vs-rest-for-ai-agents . Ordering is fully autonomous. Funding the balance isn't — not yet. Right now someone puts crypto on the balance once USDC/USDT, or a card on-ramp , and from that point the agent orders, scales and cancels on its own, spending only what's there. The end state everyone pictures — an agent paying on-chain, per request, with no pre-funding — is the x402 https://www.x402.org style, and we think it's where this goes. We haven't wired it up. It needs USDC-settled rails and a few things we don't run today, so rather than slap "fully autonomous payments" on the box, here's the truth: autonomous ordering now, autonomous funding later. The prepaid balance is the bridge, and honestly it doubles as a spend cap you probably want anyway. The MCP server speaks Streamable HTTP at https://mcp.eqvps.com/mcp , so it drops into any MCP client without a local shim. Auth is a Bearer token the agent mints itself with register account — the same token works across MCP and REST, against the same account and balance. Sessions are tracked server-side, so a long-running agent can hold one connection and keep calling tools. One practical note from running this: treat the token and the returned root password like the secrets they are. The agent should store them, not echo them into logs or chat. The balance caps the financial blast radius; basic secret hygiene caps the rest. For now most of our actual customers are humans who happen to like paying in crypto — we're not going to pretend the web is overrun with autonomous agents buying servers. But the direction is clear. As agents take on longer, real tasks, "can it get and run its own infrastructure?" stops being a party trick and becomes a requirement. When that day fully arrives, the rails need to already be there. They are. Add the MCP server to your agent — start with connecting an MCP client https://dev.to/blog/connect-eqvps-mcp-client — fund a small balance, and let it rent its first server. About a minute to root. Yes — the ordering part is fully autonomous. Over our MCP server the agent calls register account to get a token, then order vps, which spends from a prepaid balance and provisions the VPS. It reads back SSH access from get vps status. No human clicks through a checkout. The one thing a human or a funded agent wallet does first is put crypto on the balance; after that the agent runs on its own. From a prepaid balance. You fund it once with USDC or USDT or a card via the on-ramp , and order vps debits that balance per order. The agent never holds your wallet keys, and it can't spend more than what's on the balance — which is also your safety cap. MCP Model Context Protocol lets an agent call tools directly inside clients like Claude, Cursor or Cline. 'MCP provisioning' just means the whole rent-a-server flow — register, pay, order, get root — is exposed as MCP tools the agent calls itself, instead of a web dashboard a person clicks. Ordering is. Funding isn't quite there yet: today someone tops up the balance with crypto, and then the agent is autonomous. Fully on-chain per-request payment the x402 style is on our radar but not wired up — we'd rather say that plainly than pretend. Just the MCP server URL https://mcp.eqvps.com/mcp https://mcp.eqvps.com/mcp added to its client. It calls register account and gets a Bearer token in the response — no email confirmation, no human step. From there every action is a tool call. Originally published at eqvps.com.