Documentation
Connect our MCP server once and an AI assistant can deploy, list, and manage your sites directly — with a token that can publish, but can never touch billing or delete your account.
MCP — the Model Context Protocol — is an open standard that lets an AI assistant call real tools instead of only producing text. Our MCP server exposes a small set of deploy tools through that standard, so any assistant that speaks MCP can publish to your Lemonade Host account directly, from inside the conversation. See the MCP server page for the fuller walkthrough.
MCP is a standard way for an AI assistant to discover and call tools exposed by a server, the same way it might call a function in code. Our MCP server is that server — it exposes a handful of deploy-related tools, and any MCP-capable assistant that connects to it can call them.
| Tool | What it does |
|---|---|
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 your account |
That's the entire tool surface — five tools, nothing hidden. None of them can see or change billing, and none of them can delete the account itself; more on that below.
From your account, create a token scoped to deploying — not a copy of your login.
Add the Lemonade Host MCP server to your assistant's configuration, along with the token.
Restart or reload your assistant so the five tools appear, then ask it to deploy in plain language.
An assistant that can deploy is useful. An assistant that can also touch money is a different risk entirely, so the token it uses is deliberately narrow:
set_custom_domain can point a domain at a site, but turning on the paid add-on still asks a human to confirmThe line in one sentence: a Lemonade Host token can publish. It can never spend, and it can never close the account.
Someone finishes a small site inside their assistant, then asks it to publish — without leaving the conversation:
The assistant called deploy_site, got back a live URL, and the conversation continues — no dashboard, no separate login.
Keep reading
Join the list and we'll email you just once — that's the only thing we use your address for.