CloudPloy — MCP Deployment Platform for AI Coding Agents

What is CloudPloy?

CloudPloy is a deployment platform whose primary interface is not a dashboard but the Model Context Protocol. Instead of clicking through a cloud console, you point an AI coding agent — Claude, ChatGPT, Cursor, or OpenCode — at CloudPloy's MCP endpoint (app.cloudploy.com/mcp), and the agent provisions servers, deploys applications from git repos, and manages them on your behalf. The pitch is deployment without DevOps work: the site states no DevOps experience is needed, while noting that agent actions are limited to the abilities you grant through scoped tokens.

Under the hood it is a polyglot platform: builds run through Nixpacks, which covers Node, Python, Go, Rust, Ruby, Java, PHP, Deno, and static sites, with one-click presets for WordPress and Laravel. CloudPloy handles SSL, containers, and routing, and exposes environment variables, domains, logs, and a full API for power users. Provider coverage spans AWS, custom VPS, and Google Compute Engine, with the site promising more services are coming soon.

How CloudPloy Works

The workflow is three steps. First, connect the app — install the MCP integration and sign in via the browser. Second, point your AI client at the MCP address using a scoped API token issued over MCP HTTP transport. Third, deploy: the agent calls CloudPloy's MCP tools — list_servers, list_apps, deploy_app, estimate_cost, get_account, provision_server, stop_server, get_server — to inspect infrastructure, provision a box, and ship the repo.

Compute is billed at the cloud provider's exact rate from prepaid credits, with no markup; servers you attach yourself (BYO) never consume credits at all.

Main Features

• MCP-native deployment — a documented MCP endpoint and named tools (deploy_app, provision_server, estimate_cost, and more) that AI agents call directly.
• Polyglot Nixpacks builds — Node, Python, Go, Rust, Ruby, Java, PHP, Deno, and static sites, plus WordPress and Laravel one-click presets.
• Managed runtime plumbing — SSL certificates, containers, and routing handled by the platform; env vars, domains, and logs manageable from the agent or API.
• Scoped API tokens — agent access is limited to explicitly granted abilities over MCP HTTP transport.
• Provider-cost billing — prepaid credits charged at the provider's exact rate, no markup; BYO servers are free of credit consumption.
• Full REST API — the same operations available programmatically for scripts and power users.

Pricing

Four tiers are published. The free-forever plan includes 1 server, 1 app, and a maximum of 2 vCPU / 2 GB RAM — larger machines are not available on free. Starter costs $9.99 per month for up to 3 servers, Pro is $19 per month for up to 10 servers, and Scale is $39 per month with uncapped servers. In all tiers, compute itself is billed at the provider's exact rate from prepaid credits with no markup, so CloudPloy's fee is for the control plane, not the machines.

Common Use Cases

• Agent-driven deployment — a developer working in Claude or Cursor ships a repo to a fresh VPS without leaving the chat.
• Prototype hosting — spinning up small app servers on the free tier for demos and side projects.
• Cost estimation before deploy — asking the agent to run estimate_cost so infrastructure spend is known before provisioning.
• Self-hosted app management — deploying WordPress or Laravel presets onto a BYO VPS with SSL and routing handled.

Limitations

The reliability model is the sharpest edge: if prepaid credits reach zero, CloudPloy stops provisioned servers and destroys them after a 7-day grace period — an unforgiving policy for anyone who forgets to top up. BYO servers keep running on that event, but CloudPloy-side routing, SSL, and deploys stop when the plan lapses. Provider coverage is limited to AWS, GCE, and custom VPS, with everything else "coming soon." The operator is anonymous — no company, maker, or country is stated, only a © 2026 notice and a 70+ person waitlist, marking this as an early-stage product — and no uptime, SLA, or security-certification information is published. Granting an AI agent infrastructure powers also demands care: the site says actions are limited to granted abilities, but the scope configuration is on the user. Finally, there is no mention of CI pipelines, preview environments, or team collaboration features.

Summary

CloudPloy is one of the clearest implementations of the agent-operated infrastructure idea: a real MCP endpoint with named tools, Nixpacks builds across ten-plus runtimes, provider-cost compute billing, and a workable free tier. For developers already living inside Claude, Cursor, or similar clients, it can genuinely remove the DevOps step from side projects and small services. The trade-offs are early-stage risk (anonymous operator, three providers, no SLA) and a strict credit policy that destroys provisioned servers seven days after credits run out — so it suits tinkerers and small teams who monitor their credits, not yet anyone running critical production workloads.