How do you put a Cursor-built app into production?

Step by step

1. 1

   Make the build pass locally

   Run the build command in Cursor's terminal (npm run build, next build, or your framework's equivalent) and let the agent fix what fails. A build that only passes in dev will fail the same way on the host.

2. 2

   Push to GitHub and add Hostwares to Cursor

   Commit and push. Create an API key at Dashboard → API Keys, then paste the MCP block into Cursor's MCP settings. Restart Cursor; the Hostwares tools appear in the tool list.

   Cursor mcp.json

   {
     "mcpServers": {
       "hostwares": {
         "url": "https://mcp.hostwares.com",
         "headers": { "Authorization": "Bearer hwk_your_key_here" }
       }
     }
   }

3. 3

   Deploy from the chat, or from the dashboard

   In Cursor: "Deploy this repo to Hostwares as my-app". The deploy tool detects the framework, returns a price and an approval link, and the build starts once the invoice is paid; get_status reports when the site is running. Without an agent: Dashboard → Deployments → New.

   A project with a Dockerfile deploys from it; one without is detected by framework. A project that is not on GitHub can be uploaded: create_upload returns a command, then deploy with the upload id.

4. 4

   Set the environment, attach the domain

   "Set DATABASE_URL and STRIPE_SECRET_KEY on my-app" calls set_env; "Point app.example.com at my-app" calls add_domain, and verify_ssl checks the certificate once the DNS record you create resolves. Need a database first? create_database returns one with its connection string.

   Variables are read at build time, so the site rebuilds after you change them; the current version keeps serving until the new build is ready.

5. 5

   Operate from the same chat

   "Why is my-app returning 502?" runs diagnose_site: status, reachability, container state and recent logs in one call. rollback_site returns to the previous build; redeploy_site rebuilds after a fix; deployment_history lists what shipped when.

Questions