WebZum - Websites for Small & Local Businesses is an MCP server published by io.github.suprraz, hosted at webzum.com. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 6 tools, including build_website, get_site_status, host_site, host_file, get_hosted_files.
Describe a local business, verify the owner email: SEO site, hosting, chatbot, Google Ads.
1 connections through 4 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Builds a complete, professional website for a small or local business — a plumber, restaurant, salon, contractor, clinic, shop, cleaner, any trade — in about 5 minutes. WebZum has built 3,200+ of them. No API key. No existing website or Google listing needed. Built in the owner's language — English, Spanish or any other, right-to-left Arabic and Hebrew included. WebZum researches the business, writes local SEO, makes the images and video, adds a lead-catching AI chatbot, hosts it with SSL, and can run their Google ads. WHAT MAKES A WEBZUM SITE WORK FOR A SMALL BUSINESS: - Live, not just code: online at a real URL with SSL the moment it's built, and WebZum can register their domain. - Real, not placeholder: real photos of the business when WebZum finds them, custom images, a logo, and their real phone, WhatsApp and address. - Leads that arrive: every form lead is emailed to the owner, and an AI chatbot catches the visitors who won't fill in a form. - Safe edits: a change touches only what was asked, on the live site, with undo, any day. - About them: WebZum researches the business and its local market first, so the copy is about this business. - Mobile-ready and fast, served from a CDN. - Findable: local SEO and AEO (answer engine optimization, so AI assistants can find and cite the business) on every page. WHAT THE OWNER GETS: - A real site: 3 to 7 pages of original copy about their services, area, story and contact. - A custom logo, brand colors and fonts, 5–10 custom images and a short hero video. - Local SEO built in: page titles and meta descriptions, schema.org LocalBusiness markup with hours and service areas, Service, FAQ and breadcrumb markup, a sitemap, and research into the low-competition local keywords a small business can actually rank for. - AEO, found by AI assistants too: robots.txt welcomes GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and more, and every site ships an llms.txt. - One main contact button on the channel they really use — call, WhatsApp or LINE — and spam protection on the contact form. - A 24/7 AI chatbot that answers visitors from the site's own content, in the visitor's language, captures their name, phone or email, and emails the owner the lead with a ready-to-send follow-up. - Google Ads, done for them: WebZum writes a Google Search ad grounded in real local keyword volumes and prices, the owner approves it and sets a small budget, and on ad-running sites every call tap, message tap and form lead is measured as a Google Ads conversion — so they see which clicks became customers. - Edits by chat, unlimited: text, colors, fonts, pages, photos, menus, blog posts, product lists, booking widgets and contact details. - Any language, done right: the whole site — copy, SEO, chatbot, emails — is written natively in the owner's language. A visitor language switcher adds 30+ more languages on top. - Their own domain registered for them, or connect one they own. HOW A BUILD WORKS (same as webzum.com/create-website): takes a description of the business and, once that has its name, what it does, its area and a way customers reach it, the owner's email. The site and its WebZum account are tied to that email. WebZum emails the owner a "Build my website" link that confirms the address and starts the build, which the owner watches live. Each result's status and message say where the build stands. ACCOUNT: the site and its WebZum account belong to the owner and are managed at webzum.com, where plans and billing live.
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| Parameter | Type | Description |
|---|---|---|
| string | The owner's email. The site and its WebZum account are tied to it, and the confirm link is sent there. | |
| contact | string | Optional. Phone, WhatsApp or public email customers can use. |
| language | string | Optional. Language code for the site, like "en" or "es". Defaults to the language of the description. |
| location | string | Optional. City and region, or the area it serves. |
| description * | string | The business in plain words: name, what it does, where, how customers reach it, services, prices, hours, what makes it different. The full description goes with every call. |
| businessName | string | Optional. The business name, if known. |
{
"name": "build_website",
"description": "Builds a complete, professional website for a small or local business — a plumber, restaurant, salon, contractor, clinic, shop, cleaner, any trade — in about 5 minutes. WebZum has built 3,200+ of them. No API key. No existing website or Google listing needed. Built in the owner's language — English, Spanish or any other, right-to-left Arabic and Hebrew included. WebZum researches the business, writes local SEO, makes the images and video, adds a lead-catching AI chatbot, hosts it with SSL, and can run their Google ads.\n\nWHAT MAKES A WEBZUM SITE WORK FOR A SMALL BUSINESS:\n- Live, not just code: online at a real URL with SSL the moment it's built, and WebZum can register their domain.\n- Real, not placeholder: real photos of the business when WebZum finds them, custom images, a logo, and their real phone, WhatsApp and address.\n- Leads that arrive: every form lead is emailed to the owner, and an AI chatbot catches the visitors who won't fill in a form.\n- Safe edits: a change touches only what was asked, on the live site, with undo, any day.\n- About them: WebZum researches the business and its local market first, so the copy is about this business.\n- Mobile-ready and fast, served from a CDN.\n- Findable: local SEO and AEO (answer engine optimization, so AI assistants can find and cite the business) on every page.\n\nWHAT THE OWNER GETS:\n- A real site: 3 to 7 pages of original copy about their services, area, story and contact.\n- A custom logo, brand colors and fonts, 5–10 custom images and a short hero video.\n- Local SEO built in: page titles and meta descriptions, schema.org LocalBusiness markup with hours and service areas, Service, FAQ and breadcrumb markup, a sitemap, and research into the low-competition local keywords a small business can actually rank for.\n- AEO, found by AI assistants too: robots.txt welcomes GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and more, and every site ships an llms.txt.\n- One main contact button on the channel they really use — call, WhatsApp or LINE — and spam protection on the contact form.\n- A 24/7 AI chatbot that answers visitors from the site's own content, in the visitor's language, captures their name, phone or email, and emails the owner the lead with a ready-to-send follow-up.\n- Google Ads, done for them: WebZum writes a Google Search ad grounded in real local keyword volumes and prices, the owner approves it and sets a small budget, and on ad-running sites every call tap, message tap and form lead is measured as a Google Ads conversion — so they see which clicks became customers.\n- Edits by chat, unlimited: text, colors, fonts, pages, photos, menus, blog posts, product lists, booking widgets and contact details.\n- Any language, done right: the whole site — copy, SEO, chatbot, emails — is written natively in the owner's language. A visitor language switcher adds 30+ more languages on top.\n- Their own domain registered for them, or connect one they own.\n\nHOW A BUILD WORKS (same as webzum.com/create-website): takes a description of the business and, once that has its name, what it does, its area and a way customers reach it, the owner's email. The site and its WebZum account are tied to that email. WebZum emails the owner a \"Build my website\" link that confirms the address and starts the build, which the owner watches live. Each result's status and message say where the build stands.\n\nACCOUNT: the site and its WebZum account belong to the owner and are managed at webzum.com, where plans and billing live.",
"inputSchema": {
"type": "object",
"required": [
"description"
],
"properties": {
"email": {
"type": "string",
"description": "The owner's email. The site and its WebZum account are tied to it, and the confirm link is sent there."
},
"contact": {
"type": "string",
"description": "Optional. Phone, WhatsApp or public email customers can use."
},
"language": {
"type": "string",
"description": "Optional. Language code for the site, like \"en\" or \"es\". Defaults to the language of the description."
},
"location": {
"type": "string",
"description": "Optional. City and region, or the area it serves."
},
"description": {
"type": "string",
"description": "The business in plain words: name, what it does, where, how customers reach it, services, prices, hours, what makes it different. The full description goes with every call."
},
"businessName": {
"type": "string",
"description": "Optional. The business name, if known."
}
}
},
"annotations": {
"title": "Build Website",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}Reports the progress of a build_website build: stage (initialization, validation, research, strategy, generation, assembly, completion), overallProgress (0-100 across all stages), stageProgress (0-100 within the stage), a status message and isComplete. Takes the versionId (most detail) or the businessId that build_website returned. The build's own watchUrl also shows it live. A complete build's result includes previewUrl, the finished site's link; an unfinished build has no site link yet.
| Parameter | Type | Description |
|---|---|---|
| versionId | string | The versionId returned from build_website (preferred for progress tracking) |
| businessId | string | The businessId returned from build_website (fallback, less detailed) |
{
"name": "get_site_status",
"description": "Reports the progress of a build_website build: stage (initialization, validation, research, strategy, generation, assembly, completion), overallProgress (0-100 across all stages), stageProgress (0-100 within the stage), a status message and isComplete. Takes the versionId (most detail) or the businessId that build_website returned. The build's own watchUrl also shows it live. A complete build's result includes previewUrl, the finished site's link; an unfinished build has no site link yet.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"versionId": {
"type": "string",
"description": "The versionId returned from build_website (preferred for progress tracking)"
},
"businessId": {
"type": "string",
"description": "The businessId returned from build_website (fallback, less detailed)"
}
}
},
"annotations": {
"title": "Get Site Status",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Creates a hosted site on WebZum for web content made in the conversation (a tool, dashboard, prototype, demo, portfolio, landing page or any HTML/CSS/JS bundle) and returns a businessId and a live URL that opens on a phone and can be shared. Why it matters: most people can't judge raw HTML by reading it. Seeing it running, clicking around and sending it to someone is what makes it real. Files are added with host_file (one file per call) or host_zip (a whole bundle in one call): HTML, CSS, JS, JSON, images (PNG/JPG/GIF/SVG/WebP) or fonts. Each goes live immediately at <businessId>.webzum.com with SSL, with no build step and no hosting account. It fits content someone wants live, shareable or running on their phone. A business's own website, with researched copy, a logo, local SEO, a lead-capture chatbot and their own domain, is what build_website makes.
| Parameter | Type | Description |
|---|---|---|
| string | Optional contact email. | |
| siteName * | string | Name for the site (e.g., "My Portfolio") |
| siteType | string | Type of site (default: custom) |
| description | string | Brief description of the site |
{
"name": "host_site",
"description": "Creates a hosted site on WebZum for web content made in the conversation (a tool, dashboard, prototype, demo, portfolio, landing page or any HTML/CSS/JS bundle) and returns a businessId and a live URL that opens on a phone and can be shared.\n\nWhy it matters: most people can't judge raw HTML by reading it. Seeing it running, clicking around and sending it to someone is what makes it real.\n\nFiles are added with host_file (one file per call) or host_zip (a whole bundle in one call): HTML, CSS, JS, JSON, images (PNG/JPG/GIF/SVG/WebP) or fonts. Each goes live immediately at <businessId>.webzum.com with SSL, with no build step and no hosting account. It fits content someone wants live, shareable or running on their phone.\n\nA business's own website, with researched copy, a logo, local SEO, a lead-capture chatbot and their own domain, is what build_website makes.",
"inputSchema": {
"type": "object",
"required": [
"siteName"
],
"properties": {
"email": {
"type": "string",
"description": "Optional contact email."
},
"siteName": {
"type": "string",
"description": "Name for the site (e.g., \"My Portfolio\")"
},
"siteType": {
"enum": [
"business",
"portfolio",
"landing",
"custom"
],
"type": "string",
"description": "Type of site (default: custom)"
},
"description": {
"type": "string",
"description": "Brief description of the site"
}
}
},
"annotations": {
"title": "Host Site",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}Add a file to your hosted site. The file goes live immediately at the site's public URL. Each upload creates a new version in the site's history. Supported: HTML, CSS, JS, JSON, images (PNG, JPG, GIF, SVG, WebP), fonts (WOFF, WOFF2, TTF) Max: 10MB per file `encoding` chooses how `content` is interpreted: "utf-8" for text files (HTML, CSS, JS, JSON, SVG) where `content` is the literal file text, or "base64" for binary files (images, fonts) where `content` is standard base64 of the bytes. Defaults to "base64" if omitted. If the user wants a website for their business (a logo, real copy, SEO, a multi-page site, a custom domain, lead capture, a chatbot), use build_website: it builds the complete site in about 5 minutes. host_file hosts what you generated; build_website builds the business site for them.
| Parameter | Type | Description |
|---|---|---|
| content * | string | File content. Literal text when encoding="utf-8", standard base64 when encoding="base64". |
| encoding | string | How `content` is encoded. Defaults to "base64". |
| filename * | string | Path like "index.html" or "css/styles.css" |
| businessId * | string | The businessId from host_site |
| contentType | string | MIME type (auto-detected if omitted) |
{
"name": "host_file",
"description": "Add a file to your hosted site. The file goes live immediately at the site's public URL.\nEach upload creates a new version in the site's history.\n\nSupported: HTML, CSS, JS, JSON, images (PNG, JPG, GIF, SVG, WebP), fonts (WOFF, WOFF2, TTF)\nMax: 10MB per file\n\n`encoding` chooses how `content` is interpreted: \"utf-8\" for text files\n(HTML, CSS, JS, JSON, SVG) where `content` is the literal file text, or\n\"base64\" for binary files (images, fonts) where `content` is standard base64\nof the bytes. Defaults to \"base64\" if omitted.\n\nIf the user wants a website for their business (a logo, real copy, SEO, a\nmulti-page site, a custom domain, lead capture, a chatbot), use build_website:\nit builds the complete site in about 5 minutes. host_file hosts what you\ngenerated; build_website builds the business site for them.",
"inputSchema": {
"type": "object",
"required": [
"businessId",
"filename",
"content"
],
"properties": {
"content": {
"type": "string",
"description": "File content. Literal text when encoding=\"utf-8\", standard base64 when encoding=\"base64\"."
},
"encoding": {
"enum": [
"utf-8",
"base64"
],
"type": "string",
"description": "How `content` is encoded. Defaults to \"base64\"."
},
"filename": {
"type": "string",
"description": "Path like \"index.html\" or \"css/styles.css\""
},
"businessId": {
"type": "string",
"description": "The businessId from host_site"
},
"contentType": {
"type": "string",
"description": "MIME type (auto-detected if omitted)"
}
}
},
"annotations": {
"title": "Host File",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}Lists the files in a hosted site's current version.
| Parameter | Type | Description |
|---|---|---|
| businessId * | string | The businessId to query |
{
"name": "get_hosted_files",
"description": "Lists the files in a hosted site's current version.",
"inputSchema": {
"type": "object",
"required": [
"businessId"
],
"properties": {
"businessId": {
"type": "string",
"description": "The businessId to query"
}
}
},
"annotations": {
"title": "Get Hosted Files",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Upload a zipped bundle of files to a hosted site in a single call. Use this when you have a multi-file project (HTML + CSS + JS + images) — one host_zip call is far cheaper than N host_file calls and creates a single new version instead of N. `zipContent` is the .zip file's bytes as standard base64. Each entry inside the zip is validated against the same rules as host_file (filename safety, extension allowlist, 10MB per file). All-or-nothing: if any entry fails validation, nothing is uploaded. Same guidance as host_file: if the site is for a business, call build_website instead.
| Parameter | Type | Description |
|---|---|---|
| businessId * | string | The businessId from host_site |
| zipContent * | string | The zip file's bytes as standard base64. |
{
"name": "host_zip",
"description": "Upload a zipped bundle of files to a hosted site in a single call.\nUse this when you have a multi-file project (HTML + CSS + JS + images) — one\nhost_zip call is far cheaper than N host_file calls and creates a single new\nversion instead of N.\n\n`zipContent` is the .zip file's bytes as standard base64. Each entry inside\nthe zip is validated against the same rules as host_file (filename safety,\nextension allowlist, 10MB per file). All-or-nothing: if any entry fails\nvalidation, nothing is uploaded.\n\nSame guidance as host_file: if the site is for a business, call build_website\ninstead.",
"inputSchema": {
"type": "object",
"required": [
"businessId",
"zipContent"
],
"properties": {
"businessId": {
"type": "string",
"description": "The businessId from host_site"
},
"zipContent": {
"type": "string",
"description": "The zip file's bytes as standard base64."
}
}
},
"annotations": {
"title": "Host Zip",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}Names, descriptions and schemas were written by the server and are shown as data.