Your AI builds real hosted websites: describe it, get a live site with SSL, forms, analytics. Free.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Insert a component from the site's shared library into one or more existing pages, INSTEAD of hand-writing the markup yourself — the classes are already styled and themed to this site's colours. Choices: sc-page-title (the page's one <h1>), sc-gallery (cross-fading photo reel — needs 'images'), sc-info-tiles (title + picture + text sections — needs 'tiles'), sc-instructions (numbered/titled steps, optionally with a button each — needs 'tiles'), sc-event (one dated thing: a class, a session, an opening — needs 'title'), sc-btn (a link styled as a button — needs 'label'). NOT offered: sc-header/sc-footer (the site's own shell already emits those) or sc-hero (placed once, on the home page, by the site's own build). 'anchor' says where it goes: {"type": "heading", "value": "<text on the page>", "position": "after"} (default), {"type": "id", "value": "<element id>", "position": "after"}, {"type": "main_end"} (append at the end of the page), or {"type": "replace", "value": "<class of an existing sc-* block>"}. 'pages' is "all" or a list of paths from list_site_files. A page whose anchor doesn't match comes back in 'findings' with what's wrong and the fix — other pages in the same call still get the component. Follow with publish_site.
Component-specific content. sc-page-title: {text, eyebrow?}. sc-gallery: {images: [{src, alt}]}. sc-info-tiles: {tiles: [{title, img?, alt?, text}]}. sc-instructions: {title?, intro?, tiles: [{title?, body, img?, alt?, button?: [label, href]}]}. sc-event: {title, img?, meta?: [{label, value}], desc?, rsvp_href?, rsvp_label?}. sc-btn: {label, href}.
"all", or an array of page paths, e.g. ["index.html", "about.html"]
The server marks this tool as destructive. Running it may delete or overwrite data on the server or in any account you connected with your headers.
Insert a component from the site's shared library into one or more existing pages, INSTEAD of hand-writing the markup yourself — the classes are already styled and themed to this site's colours. Choices: sc-page-title (the page's one <h1>), sc-gallery (cross-fading photo reel — needs 'images'), sc-info-tiles (title + picture + text sections — needs 'tiles'), sc-instructions (numbered/titled steps, optionally with a button each — needs 'tiles'), sc-event (one dated thing: a class, a session, an opening — needs 'title'), sc-btn (a link styled as a button — needs 'label'). NOT offered: sc-header/sc-footer (the site's own shell already emits those) or sc-hero (placed once, on the home page, by the site's own build). 'anchor' says where it goes: {"type": "heading", "value": "<text on the page>", "position": "after"} (default), {"type": "id", "value": "<element id>", "position": "after"}, {"type": "main_end"} (append at the end of the page), or {"type": "replace", "value": "<class of an existing sc-* block>"}. 'pages' is "all" or a list of paths from list_site_files. A page whose anchor doesn't match comes back in 'findings' with what's wrong and the fix — other pages in the same call still get the component. Follow with publish_site.
| Argument | Type | Description |
|---|---|---|
| name* | string | |
| slug* | string | |
| pages | any | "all", or an array of page paths, e.g. ["index.html", "about.html"] |
| anchor* | object | |
| fields* | object | Component-specific content. sc-page-title: {text, eyebrow?}. sc-gallery: {images: [{src, alt}]}. sc-info-tiles: {tiles: [{title, img?, alt?, text}]}. sc-instructions: {title?, intro?, tiles: [{title?, body, img?, alt?, button?: [label, href]}]}. sc-event: {title, img?, meta?: [{label, value}], desc?, rsvp_href?, rsvp_label?}. sc-btn: {label, href}. |
{
"type": "object",
"required": [
"slug",
"name",
"anchor",
"fields"
],
"properties": {
"name": {
"enum": [
"sc-page-title",
"sc-gallery",
"sc-info-tiles",
"sc-instructions",
"sc-event",
"sc-btn"
],
"type": "string"
},
"slug": {
"type": "string"
},
"pages": {
"oneOf": [
{
"enum": [
"all"
],
"type": "string"
},
{
"type": "array",
"items": {
"type": "string"
},
"minItems": 1
}
],
"description": "\"all\", or an array of page paths, e.g. [\"index.html\", \"about.html\"]"
},
"anchor": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"enum": [
"heading",
"id",
"main_end",
"replace"
],
"type": "string"
},
"value": {
"type": "string",
"description": "heading text / element id / class to replace — not used for main_end"
},
"position": {
"enum": [
"before",
"after"
],
"type": "string",
"description": "for heading/id anchors, default after"
}
}
},
"fields": {
"type": "object",
"description": "Component-specific content. sc-page-title: {text, eyebrow?}. sc-gallery: {images: [{src, alt}]}. sc-info-tiles: {tiles: [{title, img?, alt?, text}]}. sc-instructions: {title?, intro?, tiles: [{title?, body, img?, alt?, button?: [label, href]}]}. sc-event: {title, img?, meta?: [{label, value}], desc?, rsvp_href?, rsvp_label?}. sc-btn: {label, href}."
}
}
}Build a brand-new hosted website from a plain-language description. RETURNS IMMEDIATELY with status 'building' — the site takes about 2-3 minutes and is NOT ready when this returns. Tell the user where it will be (expected_url) and poll get_build_status with the returned claim_token. NEVER call create_site a second time for the same site: each call builds another one. Works WITHOUT signing in: an unauthenticated call builds a guest site and returns a claim_url — the user signs up free (no card) at that link to keep it; unclaimed guest sites are deleted after 72 hours. Signed in, the site lands directly on the connected account (free tier: one site, no card).
| Argument | Type | Description |
|---|---|---|
| template | string | Optional override of the starting template. Omit it and the template is chosen from the description. |
| site_name* | string | Short human name for the site, e.g. 'Whitney Apparel'. |
| description* | string | What the site is for. MINIMUM 12 CHARACTERS — a bare 'bike shop' is rejected. Say what the business is, where it is, and what the site should include; the AI builds directly from this, so more detail means a better first result. Good: 'Oak Barrel Coffee, a small-batch roaster in Turlock CA — our story, three coffees with tasting notes and prices, and a contact form.' If the user was vague, ask them one question before calling this rather than sending two words. |
| contact_email | string | Optional, guest builds only: the user's email — we send the site link and a reminder before the unclaimed site expires. |
Ask sitectrl's AI editor to change an existing site ('add a contact page', 'make the hero darker'). Edits land in the site's draft; the first build of a brand-new site goes straight live. Returns what changed plus the draft URL.
| Argument | Type | Description |
|---|---|---|
| slug* | string | |
| instruction* | string | The change to make, in plain language. |
{
"type": "object",
"required": [
"slug",
"instruction"
],
"properties": {
"slug": {
"type": "string"
},
"instruction": {
"type": "string",
"description": "The change to make, in plain language."
}
}
}The site's private first-party traffic: pageviews/visitors/sessions/clicks totals, top pages, referrers, devices. Windows: 24h, 7d, 30d.
| Argument | Type | Description |
|---|---|---|
| slug* | string | |
| window | string |
{
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string"
},
"window": {
"enum": [
"24h",
"7d",
"30d"
],
"type": "string"
}
}
}Check whether a site started by create_site has finished. Pass the claim_token create_site returned. Works WITHOUT signing in. Poll this every 30-60 seconds rather than calling create_site again — a second create_site call builds a SECOND site.
| Argument | Type | Description |
|---|---|---|
| claim_token* | string | The claim_token from create_site. |
{
"type": "object",
"required": [
"claim_token"
],
"properties": {
"claim_token": {
"type": "string",
"description": "The claim_token from create_site."
}
}
}Details for one site: live URL, draft URL, status.
| Argument | Type | Description |
|---|---|---|
| slug* | string | The site's slug from list_sites. |
{
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "The site's slug from list_sites."
}
}
}List the files in a site's draft tree (paths + sizes).
| Argument | Type | Description |
|---|---|---|
| slug* | string |
{
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string"
}
}
}List the user's sitectrl sites with their live URLs and hosting platform.
No arguments.
{
"type": "object",
"properties": {}
}Publish the site's draft to the LIVE site (hosted sites). A snapshot of the previous live version is taken first, so it's undoable.
| Argument | Type | Description |
|---|---|---|
| slug* | string |
{
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string"
}
}
}Read one file from a site's draft tree (text, or base64 for binary; 512 KB cap).
| Argument | Type | Description |
|---|---|---|
| path* | string | |
| slug* | string |
{
"type": "object",
"required": [
"slug",
"path"
],
"properties": {
"path": {
"type": "string"
},
"slug": {
"type": "string"
}
}
}Search real domain availability + prices (com/net/org/co/io/site and more). Available results include a purchase_url — hand it to the USER to complete checkout; the connector never spends money. Purchased domains connect to their sites in one click.
| Argument | Type | Description |
|---|---|---|
| query* | string | Domain or name to check, e.g. 'sierratrailcoffee.com'. |
{
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "Domain or name to check, e.g. 'sierratrailcoffee.com'."
}
}
}The connected sitectrl account: email, plan status, free-site slot, and credit balance.
No arguments.
{
"type": "object",
"properties": {}
}Push files (HTML/CSS/JS/images) into a site's DRAFT — use this when YOU are writing the code yourself instead of asking sitectrl's AI. Text files go in 'content'; binary files (images/fonts) in 'content_base64'. Max 40 files/call, 2 MB/file. Keep the <script defer src="sc-track.js"></script> include on every HTML page (the site's built-in private analytics — publish re-adds it if missing). Use clearly-marked placeholder contact info unless the user provided real details. For working forms, POST to /_sc/form/submit with a hidden _form name field — submissions reach the owner's dashboard + email (never use mailto:). Every HTML file is checked before it's written (DOCTYPE, charset, and any invariant this site has declared) — a file that fails is refused and comes back in 'refused' with what's wrong and the exact fix; other files in the same call still write. Follow with publish_site to go live.
| Argument | Type | Description |
|---|---|---|
| slug* | string | |
| files* | array |
{
"type": "object",
"required": [
"slug",
"files"
],
"properties": {
"slug": {
"type": "string"
},
"files": {
"type": "array",
"items": {
"type": "object",
"required": [
"path"
],
"properties": {
"path": {
"type": "string",
"description": "Relative path in the site, e.g. index.html or css/style.css"
},
"content": {
"type": "string"
},
"content_base64": {
"type": "string"
}
}
}
}
}
}{
"type": "object",
"required": [
"site_name",
"description"
],
"properties": {
"template": {
"enum": [
"local-services",
"restaurant",
"shop",
"portfolio",
"classes",
"community"
],
"type": "string",
"description": "Optional override of the starting template. Omit it and the template is chosen from the description."
},
"site_name": {
"type": "string",
"description": "Short human name for the site, e.g. 'Whitney Apparel'."
},
"description": {
"type": "string",
"minLength": 12,
"description": "What the site is for. MINIMUM 12 CHARACTERS — a bare 'bike shop' is rejected. Say what the business is, where it is, and what the site should include; the AI builds directly from this, so more detail means a better first result. Good: 'Oak Barrel Coffee, a small-batch roaster in Turlock CA — our story, three coffees with tasting notes and prices, and a contact form.' If the user was vague, ask them one question before calling this rather than sending two words."
},
"contact_email": {
"type": "string",
"description": "Optional, guest builds only: the user's email — we send the site link and a reminder before the unclaimed site expires."
}
}
}