Developers
Build on MakeMySiteLive
Everything you can do in the dashboard, you can do in code. Drive deploys from a public REST API, or let an AI agent do it through our hosted MCP server.
REST API
Base URL https://www.makemysitelive.com. Authenticate every request with a scoped key: Authorization: Bearer mmsl_…
curl -X POST https://www.makemysitelive.com/v1/sites \
-H "Authorization: Bearer mmsl_your_key" \
-H "Content-Type: application/json" \
-d '{"subdomain":"my-site","name":"My Site"}'curl -X POST https://www.makemysitelive.com/v1/sites/SITE_ID/deploy \
-H "Authorization: Bearer mmsl_your_key" \
-H "Content-Type: application/zip" \
-H "X-File-Name: site.zip" \
--data-binary @site.zip# A large ZIP can outlast a proxy's timeout. Ask for a background deploy:
curl -X POST "https://www.makemysitelive.com/v1/sites/SITE_ID/deploy?async=true" \
-H "Authorization: Bearer mmsl_your_key" \
-H "Content-Type: application/zip" \
-H "X-File-Name: site.zip" \
--data-binary @site.zip
# 202 {"status":"processing","deployId":"…","statusUrl":"/v1/sites/SITE_ID/deploys/…"}
# Poll until status is "succeeded" or "failed":
curl https://www.makemysitelive.com/v1/sites/SITE_ID/deploys/DEPLOY_ID \
-H "Authorization: Bearer mmsl_your_key"curl -X POST https://www.makemysitelive.com/v1/microsites \
-H "Authorization: Bearer mmsl_your_key" \
-H "Content-Type: application/json" \
-d '{"subdomain":"my-page","name":"My Page","html":"<!doctype html><h1>Live</h1>"}'| Method | Endpoint | What it does | Scope |
|---|---|---|---|
| GET | /v1/me | Your account | account:read |
| GET | /v1/sites | List full sites | sites:read |
| GET | /v1/sites/{id} | Site + version history | sites:read |
| GET | /v1/check-subdomain?name= | Check availability | sites:read |
| POST | /v1/sites | Create a full site | sites:write |
| POST | /v1/sites/{id}/deploy | Deploy a ZIP (raw body). Add ?async=true to run it in the background | sites:write |
| GET | /v1/sites/{id}/deploys/{deployId} | Progress of a background deploy | sites:read |
| POST | /v1/sites/{id}/rollback | Roll back to a version | sites:write |
| PATCH | /v1/sites/{id}/protection | Password protection (paid) | sites:write |
| POST | /v1/sites/{id}/tier | Switch FREE / PAID | sites:write |
| POST | /v1/sites/{id}/subdomain | Rename the subdomain | sites:write |
| DELETE | /v1/sites/{id} | Delete a site | sites:delete |
| GET | /v1/microsites | List microsites | sites:read |
| GET | /v1/microsites/{id} | Microsite + version | sites:read |
| POST | /v1/microsites | Create & publish from HTML | sites:write |
| POST | /v1/microsites/{id}/deploy-html | Republish microsite HTML | sites:write |
API key scopes (least privilege)
- account:read
- View account details
- sites:read
- List and inspect sites
- sites:write
- Create, deploy, roll back, rename, protect
- sites:delete
- Permanently delete sites
Start building
Create a free account, generate a key, and deploy your first site from code.
Create your free accountPublishing limits
To keep the service fair, each account and each IP address can publish a limited number of times a day.
- Each account can deploy 10 times in 24 hours, or 50 times when you deploy to a paid site. Dashboard uploads, REST API deploys, MCP updates and upload links all count toward the same total, for full sites and microsites alike.
- Each IP address can also deploy to free sites 10 times in 24 hours, and to paid sites 100 times, however many accounts use it.
- Only successful uploads use up your allowance, including submissions saved for review. An upload that is rejected, such as a ZIP without an
index.html, does not. - Creating a new microsite through the dashboard or REST API has its own limit: 5 a day per IP address. It does not use up your deploys.
- New accounts get 2 free microsites. When all are used, creating another answers
403with a link to add a microsite slot ($1 a month or $10 a year each). Older accounts keep the allowance they have. A publish that is rejected on the first try does not keep a slot. - If you hit a limit, the API answers
429with aRetry-Afterheader and a message saying which limit you reached. The header is the number of seconds left before you can try again. Wait that long, then retry. - Deploy when your content changes, not on a timer. A script that republishes a live page every few minutes will use up the day's deploys quickly.
MCP server
Connect an MCP-capable AI client (like Claude) to our hosted server and an agent can create, deploy, roll back, and protect your sites by chatting, within your plan.
Add it as a remote connector in your client and sign in with your MakeMySiteLive account (OAuth). Grant read-only or read-write access. The agent acts only as you. It exposes read tools (account, list, inspect, check-subdomain) and, with write access, create / deploy / rollback / password-protection / delete.
Read the MCP guide →https://mcp.makemysitelive.com/mcp