MCP server
Connect our MCP server once and your assistant creates the site, publishes the files, checks it went live, and hands you back a URL — without you opening a dashboard. 99¢ a month for the site it lands on, and the token it uses can never touch billing.
deploy_site({ site: "portfolio", dir: "./dist" }) → 42 files uploaded ✓ live at portfolio.lemonhosted.com
The problem
Built in the chat. Stuck in the chat.
A huge share of small sites now get made start to finish inside a conversation — described, built, refined, approved. Then they stall there, done but homeless, because putting one online was always the step an assistant had to hand back to you. That's the step the MCP server takes over: you say publish, and it publishes.
In plain English
MCP is an open standard that lets an AI assistant use real tools instead of only producing text. Our server gives it five, so any assistant that speaks MCP can work in your account directly — no dashboard, no second login, nothing to copy and paste between windows.
deploy_site — puts a folder of pages online, or updates what's already therelist_sites — returns the site the token reaches, and how it's doingget_deploy_status — says whether a publish is going out or liveThree tools, and that is the whole surface. Nothing here deletes a site, moves a domain, or touches billing. An assistant holding your token can publish to one site and read that site's status — it cannot spend your money, cancel anything, or reach another site. That boundary is what makes handing a token to an autonomous agent a reasonable thing to do.
Join the list// the assistant calls the tool directly deploy_site({ site: "petloop", dir: "./dist" }) // → response { status: "queued", url: "https://petloop.lemonhosted.com" }
Connecting it
Add the Lemonade Host MCP server to your assistant's configuration, along with a scoped token generated from your account.
Restart or reload it so the five tools show up alongside whatever else it already has access to.
Describe what you want in plain language. The assistant calls deploy_site and hands you back a live URL.
The part that matters
An assistant that can publish for you is useful. An assistant that could also spend your money is a different proposition entirely — so the token it holds simply doesn't reach that far.
A token can create, update, check the status of, and remove a single site — nothing more than that.
Tokens can't see or change billing details, no matter what the assistant is asked to do.
An assistant can remove a single site. It can never delete the account underneath it.
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
Someone finishes a small site in their assistant, says put it online, and reads the address back a few seconds later — no new tab, no dashboard, no export step in between.
Questions
Any assistant that speaks MCP, the open standard, can call these tools once you add the server — it isn't limited to one product.
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.
The tools stop responding to that token immediately. Nothing about your live sites changes — revoking a token only turns off future deploys through it.
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?
Start from a template, change the words in your browser, press publish.
Connect a repository once. Every push after that puts the new version live.
Just the files, dropped straight into the browser.
npx lemonade-host deploy, from wherever your files already are.
See what every site includes, or check pricing — 99¢ a month per site, cancel any time.