Closed beta guide

What you can deploy in the SiteDropper closed beta

3 min read

Who the SiteDropper closed beta is for and how early users can deploy local apps through Codex, Claude, Cursor, and more via MCP, ZIP uploads, or REST API automation.

Use SiteDropper when you need a link quickly

The closed beta is focused on a simple promise: take the project you already have and turn it into a live URL without the cloud setup hassle. It is a good fit for prototypes, client demos, AI-generated apps, docs sites, internal tools, and small web services.

  • You have local files or a ZIP archive that should be online quickly.
  • You want to share a working demo before investing in full infrastructure.
  • You want an agent, dashboard, or script to handle the deploy steps for you.

Choose the workflow that matches your team

Different builders want different deployment surfaces. SiteDropper supports MCP for coding agents, dashboard ZIP upload for humans, and REST API automation for scripts and internal tools.

  • MCP is best when you want Codex, Claude Code, Cursor, and more to deploy from the coding loop.
  • ZIP upload is best when you want to drag and drop a project from the browser.
  • REST API automation is best when repeatable deploys should run from CI or an internal workflow.

Keep control over sharing

A deployment is only useful if the right people can see it at the right time. Start with draft or private visibility while testing. Share more broadly only after you have opened the live URL and confirmed the app behaves the way you expect.

Want to go Local to Live from your tools?

Request closed beta access and tell us whether you want to launch from Codex, Claude, Cursor, and more via MCP, a ZIP upload, or the REST API.