Overview

Last updated: June 20, 2026

Your AI assistant already writes your software. On American Cloud, it can deploy and operate it too.

These pages are recipes: each one gives you a battle-tested prompt to paste into your assistant — Claude Code, Cursor, or any MCP client — plus a step-by-step account of what the assistant will do with it. The assistant does the work through the American Cloud MCP server; you review and confirm.

[ claude code · deploy with one sentence ]
Cost shown first, you approve, then it builds.

Before you start

  1. Set up the MCP server for your client — Claude Desktop, Claude Code, Cursor, or others.
  2. Deployments create real resources, so you'll need a read-write API key and the --allow-writes flag — see the overview for how both fit together.
  3. For deploy workflows, a coding agent (Claude Code) is the strongest pairing: it combines American Cloud tools with a terminal, so it can provision a server and deploy to it in one conversation.

Every recipe follows the same rule: the assistant shows you a cost estimate before creating anything. You always know the monthly price before a resource exists.

Deployment recipes

Migration playbooks

Moving from another platform? The assistant inventories what you have, proposes the American Cloud equivalent with a cost estimate, and executes the move in phases — with a DNS cutover at the end, not a leap of faith at the start.

[ claude code · migrate in one conversation ]
Price the equivalent first, build on approval, cut over on your timeline.

Teach your agent the way here

Add one file to your repository and any AI coding agent knows how to deploy that project to American Cloud — conventions, canonical flows, cost-estimate-first behavior included:

Looking for ideas first?

Things to try with the MCP server collects smaller prompts — audits, cost reviews, incident triage — that work with a read-only key and zero risk.