AI & publishing
Deploy a Cursor or Claude Code project straight from the terminal
1 September 2026 · 2 min read
Cursor and Claude Code write real files on your machine, not a preview locked inside a chat window. That's an advantage the moment you want to publish, because there's nothing to export first: the folder your AI tool just built is already what a host needs. Here's the fastest way to turn it into a live link without leaving the terminal.
What you're starting with
If your project is a static site, plain HTML/CSS/JS, or a static export from a framework, you already have everything required to publish. Check for an index.html at the top level of the folder; that's the one file every static host needs to find.
Publish with the CLI
MakeMySiteLive's CLI is built for exactly this: publishing from the terminal you're already working in.
npm i -g @mmsl/cli mmsl login mmsl_your_api_key mmsl create yourname mmsl deploy <siteId> ./your-project-folder
The deploy command accepts either a folder or a .zip file, so there's no manual zipping step first. The API key comes from /dashboard/api-keys in your account. It's live at yourname.makemysitelive.com by the time the command finishes, with free SSL already on.
Or skip the CLI with MCP
If you're working in Claude Code specifically and would rather not install anything, MakeMySiteLive also runs a hosted MCP server. Connect one URL and Claude can create the site, deploy it, and hand you the live link in the same session, no separate terminal command needed.
What you get either way
A free subdomain with HTTPS from the first deploy and retained full-site versions so you can roll back a recent bad one. Upgrading the full site to Pro adds custom-domain and password-protection options without changing how you build the project itself.
Key takeaways
- ✓If your AI tool already writes files to disk (Cursor, Claude Code, or similar), you already have what a static host needs, no export step first.
- ✓The CLI (npm i -g @mmsl/cli) deploys a folder or ZIP straight from the terminal in one command.
- ✓Claude Code users can skip the CLI entirely and publish through MakeMySiteLive's MCP connector instead.
- ✓Every full-site deploy is versioned and instantly live with free SSL, whichever path you use.
Frequently asked questions
Do I need to zip my project before deploying?
No. The CLI's deploy command accepts either a folder path or a .zip file directly.
Where do I get an API key for the CLI?
Create one from /dashboard/api-keys in your MakeMySiteLive account, then save it with mmsl login or set it as the MAKEMYSITELIVE_API_KEY environment variable for CI.
Can I use this in a CI pipeline instead of my local terminal?
Yes. Install the CLI and run mmsl deploy in any CI job, using the API key as a secret environment variable instead of logging in interactively.
What if I'm using Claude Code instead of Cursor?
Either the CLI or the MCP connector works. The MCP path lets Claude publish directly from the conversation without you running a command yourself.