Documentation
Connect our MCP server once and an AI assistant can deploy, check and restore your site 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. This page walks through connecting it step by step; for an overview of what an assistant can do with it, see the MCP server page.
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 files to the one site the token belongs to, replacing what is live. The previous version stays restorable for 7 days |
get_site_files | Reads the files currently live, so an assistant can change a site without wiping the parts it never saw |
list_sites | Shows that one site - its address and current status |
get_deploy_status | Recent deploys: when, how they arrived, whether they worked, and why if they didn't |
restore_release | Puts a previous release back online. The undo for a deploy that went wrong |
trash_site | Takes the site offline into the trash, restorable for 30 days. Nothing is deleted |
That's the entire tool surface - six tools, nothing hidden. None of them can see or change billing, and none of them can touch another site or 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 six 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:
trash_site has to be handed the site's exact address to work, so it cannot fire without something having looked at which site is about to go offlineThe 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.
The full reference for the tools, what a token can reach, and how to undo a deploy is in the help center: MCP, for AI assistants.
Keep reading
A real website for 99¢ a month. Start from a template or bring your own.