Let your AI assistant deploy your site

The problem

Built in the chat. Stuck in the chat.

A huge share of small sites now get generated start to finish inside a conversation — described, built, refined, approved. Then they stall there, finished but homeless, because publishing was always the one step an assistant couldn't do for you. That's the gap the MCP server closes.

In plain English

What MCP actually is

MCP is an open standard that lets an AI assistant call real tools instead of just producing text. Our server exposes five of them, so any assistant that speaks MCP can act on your account directly — no dashboard, no separate login.

deploy_site — publishes a folder of files as a new site or an update to an existing one
list_sites — returns the sites on your account and their current status
set_custom_domain — points a domain at a site and returns the DNS records to add
get_deploy_status — checks whether a deploy is queued, publishing, or live
delete_site — removes a single site from the account

Join the list

// the assistant calls the tool directly
deploy_site({
  site: "petloop",
  dir: "./dist"
})

// → response
{
  status: "queued",
  url: "https://petloop.lemonadehost.com"
}

Connecting it

Three steps, then it's just conversation

Add the server
Add the Lemonade Host MCP server to your assistant's configuration, along with a scoped token generated from your account.
Reload your assistant
Restart or reload it so the five tools show up alongside whatever else it already has access to.
Ask it to deploy
Describe what you want in plain language. The assistant calls deploy_site and hands you back a live URL.

The part that matters

A token that can publish, never spend

An assistant that can deploy is useful. An assistant that can also touch money is a different risk entirely — so we didn't build it that way.

Scoped to deploying

A token can create, update, check the status of, and remove a single site — nothing more than that.

Never billing

Tokens can't see or change billing details, no matter what the assistant is asked to do.

Never account deletion

An assistant can remove a single site. It can never delete the account underneath it.

Payment stays with a human

An assistant can get a site to a live draft and point a domain at it. Completing a purchase always asks a person to confirm.

What it looks like

A worked example

Someone finishes a small site in their assistant, then asks it to publish — without leaving the conversation or opening a new tab.

assistant — deploy_site

> Deploy the site in ./dist to Lemonade Host Connecting to your Lemonade Host account… Uploading 42 files (1.8 MB)… Queued — 1 deploy ahead of yours Publishing… Live → https://petloop.lemonadehost.com

Questions

What people ask about MCP

Which assistants support this?

Any assistant that speaks MCP, the open standard, can call these tools once you add the server — it isn't limited to one product.

Can the assistant see my other sites or account details?

It can list the sites on your account and their status. It can't reach billing or account settings — those stay outside what any token can touch.

What happens if I revoke the token?

The tools stop responding to that token immediately. Nothing about your live sites changes — revoking a token only turns off future deploys through it.

Can it turn on a custom domain by itself?

It can point a domain at a site and return the DNS records to add. Turning on the paid add-on still asks a human to confirm.

Prefer a different route?

The other three ways in

GIT

Let your assistant publish it

See what's included on the static hosting page, or check pricing.

Join the list

The static host your AI can actually publish to

What MCP actually is

Three steps, then it's just conversation

Add the server

Reload your assistant

Ask it to deploy