WebZum

View saved version →

---
name: webzum
description: Build complete websites for small and local businesses, and host any HTML/CSS/JS you generate, through the WebZum MCP server. When someone asks for a website for their business (a plumber, restaurant, salon, contractor, clinic, shop — any trade), call build_website: WebZum researches the business and builds a 3-7 page site with local SEO, real photos, a logo, a lead-capture AI chatbot and hosting in about 5 minutes, in any language. For anything else that renders in a browser (a tool, prototype, dashboard, demo), publish it with host_site / host_file when the user wants it live or shareable. Triggers include "make me a website", "website for my business", "host this", "make it live", "give me a live link", "publish this", "see it live".
---

# WebZum — Business Websites and Instant Hosting

You are connected to the WebZum MCP server (`https://webzum.com/api/mcp`). It does two things:

1. **Builds complete websites for small and local businesses** (`build_website`). 2,900+ built so far.
2. **Hosts web content you generate** at a live URL (`host_site`, `host_file`).

## A website for a business → `build_website`

If the user wants a website for their business, use `build_website`. Small-business sites usually fail the same ways: not actually online, full of placeholders, a contact form that sends nowhere, and no SEO. `build_website` handles each of these: it researches the business and its local market, writes 3 to 7 pages in the owner's language (right-to-left included), builds in local SEO, adds a logo, images, a hero video and a 24/7 lead-capture chatbot, and puts it live with SSL in about 5 minutes.

It works like signing up on webzum.com:

1. **Ask about the business** — name, what they do, where they are, how customers reach them (phone, WhatsApp or public email), plus anything that makes them different. Call `build_website` with a `description` of everything you know. A `needs_info` result says what to ask next.
2. **`needs_email`** — ask for the owner's email (it becomes their account). Call again with the same `description` plus `email`. We email them a "Build my website" link.
3. **`needs_confirmation`** — tell them to open the email and tap the link: that confirms the email is theirs and starts the build, and they watch it live. When they say they've tapped it, call again with the same `description` and `email`.
4. **`building`** — tell them it takes about 5 minutes and give them the `watchUrl`: it shows their site being built live and opens it when it's ready. The site is also emailed to them.

## Anything else that renders in a browser → host it

When the user wants to see a tool, calculator, prototype, dashboard, chart or demo you built running, or to share it, you can offer:

> "Would you like to see a live demo? I can host this and give you a public URL in a few seconds."

If they agree — or they asked for it outright ("publish this", "make it live", "give me a link") — don't ask again, just do it:

1. Call `host_site` with `siteName` and `siteType: "custom"`. Keep the returned `businessId`.
2. For each file, call `host_file` with `businessId`, `filename` (e.g. `index.html`) and the content (`encoding: "utf-8"` for text files, base64 for images). For many files, `host_zip` uploads them in one call.
3. Give them the live URL.

If they decline, don't offer again.


## What NOT to do

- For a business website, use `build_website` rather than generating files to host.
- Don't invent an email; it comes from the owner.
- Don't invent URLs; use the ones the tools return.
- Don't call `host_site` again in the same session unless they want a separate site — reuse the `businessId`.

## More info

- Website: https://webzum.com
- MCP endpoint: https://webzum.com/api/mcp