Skip to content
sitectrl logo

sitectrl MCP server

Which servers in the official MCP registry are sitectrl's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to sitectrl

Whose server it is
  • Registry nameai.sitectrl/sitectrlverified in the MCP registry

The registry name sits under sitectrl.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools13
  • Server calls itselfsitectrl
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 669 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • create_site, edit_site, write_site_files, publish_site, add_component change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 7 of 13 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-20
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer597 ms
  • Space in an agent's context≈ 2,146 tokensthe definitions of all its tools (13), which an agent carries on every turn
  • Tool definitionsA · 91 of 100
  • Typed results0 of 13 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 7 of 13

What an agent can do with it

  • not sure · Move an existing site onto hosted infrastructure
  • not sure · Build a new site by describing it in chat
  • not sure · Review search queries and fix weak pages

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: create_site, edit_site, write_site_files, publish_site, add_component

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers13 tools · read 2026-10-20
  • whoami

    The connected sitectrl account: email, plan status, free-site slot, and credit balance.

  • list_sites

    List the user's sitectrl sites with their live URLs and hosting platform.

  • get_site

    Details for one site: live URL, draft URL, status.

  • create_site

    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

    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…

  • edit_site

    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.

  • write_site_files

    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…

  • list_site_files

    List the files in a site's draft tree (paths + sizes).

  • read_site_file

    Read one file from a site's draft tree (text, or base64 for binary; 512 KB cap).

  • publish_site

    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.

  • add_component

    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…

  • search_domains

    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…

  • get_analytics

    The site's private first-party traffic: pageviews/visitors/sessions/clicks totals, top pages, referrers, devices. Windows: 24h, 7d, 30d.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "sitectrl": {
      "type": "http",
      "url": "https://mcp.sitectrl.ai/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http sitectrl https://mcp.sitectrl.ai/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.sitectrl.ai/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.