Skip to main content

The engine

Why not just ask your AI to write a website?

We didn't add AI to a website builder. We built the engine for AI.

You can, and it will look fine on day one. The trouble starts later: a phone number that's right on one page and wrong on another, a form that looks finished but sends nothing, a change that quietly breaks a page you didn't ask it to touch. SiteShip is an engine built for AI to build on, so the site still holds up on edit number fifty.

What goes wrong, and what the engine does about it

The AI breaks something while changing something else.

Every change is checked as it's saved: 16 checks, on every write. A change that would break the site is turned back to the AI with what to fix, before you ever see it.

Your phone number is right on one page and wrong on another.

Your name, phone, address and hours are written once. Every page, and the details Google reads, come from that one place. If the AI types a fact into a page by hand, it's warned.

The contact form looks right but goes nowhere.

Forms are built in. Your AI writes a plain form; SiteShip checks what's sent, filters spam, stores every lead and emails it to you.

It needs a developer's tools to build and host.

There's no build step and nothing to install. Pages are served straight from your site's files on Cloudflare's network, so there's no build that can fail.

A half-finished change goes live.

Changes go to a private draft. A publish goes live all at once or not at all, and after your first launch your live site changes only on your click.

You can't get back to how it was.

Every change can be undone, and earlier published versions are kept so you can restore one.

Four ways to get a website from AI

AI writing plain HTML AI driving a framework (Astro, Next.js) A classic builder with AI added SiteShip
Who checks the AI's work Usually nobody The build and linters a developer sets up The editor's own limits 16 checks on every write; broken files are refused
Where business facts live Copied into each page Wherever the AI or developer puts them The builder's settings and widgets One file, feeding every page and what Google reads
Forms and leads A third-party service, or an email link A developer adds a service or writes one A built-in widget Built in: checked, spam filtered, stored and emailed
Hosting and publishing Upload files; partial updates are possible Build, then deploy; a failed build stops everything Hosted, with a publish button Hosted, no build; a publish is all at once
On edit number fifty Copies drift apart Depends on the codebase and the AI's discipline Tied to the editor's structure Same structure every time; undo and versions
Who can publish Whoever has the files Whoever can deploy Account users You. Your AI only if you allow it

A general comparison of approaches, not of any one product.

Built in, not written fresh each time

  • Forms that store and email every lead
  • Menus, tabs, pop-ups and galleries, with no custom code
  • Titles, descriptions, a sitemap and a guide for AI assistants
  • Images resized for every screen
  • A page for every item in a list, like a menu or a team
  • Redirects from your old addresses
  • A cookie consent banner
  • Undo, and earlier versions to go back to

Because every SiteShip site is built the same way, any AI can pick up where the last one left off.

We measure it

We run the same set of briefs through different AI models and score what they build. In our latest internal round, four briefs on two models produced eight sites: every named page was there, every link between lists was right, and no file was rejected.

Internal tests on our own briefs, November 2026.

46/46
named pages built
28/28
links between lists right
0
files rejected

For the technically curious

What it's made of

  • Sites are plain files: Markdown and HTML pages, Liquid templates, Tailwind for styling, data in YAML and JSON.
  • Rendered on Cloudflare Workers at the edge; no build step.
  • Your AI works through 21 tools over MCP, with a built-in guide it reads as it goes.
  • Plain JavaScript files are allowed for anything unusual.

What it doesn't do, on purpose

  • No npm packages or build tools.
  • No server-side code of your own.
  • No second CSS framework.

Those limits are what let the engine check the work.

See it build something.

Add SiteShip to your AI and have a home page in about a minute. Free to build.

Browse the galley

Built in a chat

Home page of Low Tide Coffee, a coffee shop website built with SiteShip

Coffee shop

Low Tide Coffee

The prompt that built it

Build a website for Low Tide Coffee, a small coffee shop and roastery at 14 Harbor Street, Beaufort, SC. We roast our own beans in the back room. Open every day 7am to 3pm. Phone (843) 555-0114. A menu with prices (drip, cortado, cold brew, oat-milk latte, biscuits and pastries). Two house blends sold in the shop: Marsh Blend and Dock Street Dark. Catering for offices and events, with an enquiry form (name, email, date, number of people, message). Pages: Home, Menu, Our beans, Catering. Look: warm and moody. Dark roasted brown and cream with a burnt-orange accent, an elegant serif for headlines with a clean sans for text, a photo of coffee being poured in the hero, and a menu laid out like a printed cafe menu.

Swap in your own business details. Your AI will ask five quick questions if anything is missing.

Add SiteShip to your AI

SiteShip is a connector you add once. You'll create your free account when you connect. No card needed.

https://app.siteship.ai/mcp
ChatGPT
  1. Open ChatGPT on the web and go to Settings, then Apps and connectors.
  2. Choose Add custom connector (you may need to switch on Developer mode under Advanced).
  3. Name it SiteShip, paste the address above and choose OAuth.
  4. Sign in to SiteShip when asked, then start a new chat and say: Get started with SiteShip.

Custom connectors need a paid ChatGPT plan.

Claude
Add to Claude

This opens Claude with SiteShip filled in. Click Add, sign in to SiteShip, then say: Get started with SiteShip.

Or add it by hand

  1. Open Claude and go to Customize, then Connectors.
  2. Click Add, then Add custom connector.
  3. Name it SiteShip and paste the address above.
  4. Sign in to SiteShip when asked, then start a new chat and say: Get started with SiteShip.
Grok

Go to grok.com/connectors, choose New Connector, then Custom, and paste the address above.

Gemini

In the Gemini web app, open Apps/Connectors settings, add a custom connector and paste the address above. (US accounts only for now.)

Other AI apps and coding tools
  1. Open your AI app's settings and look for Connectors, Apps, Integrations or MCP servers.
  2. Add a custom (remote) connector and paste the address above.
  3. Sign in to SiteShip when asked, then start a new chat and say: Get started with SiteShip.

Works with any app that accepts a remote MCP server, including coding tools such as Claude Code, Cursor, VS Code and Codex.

Coding tools

Claude Code

claude mcp add --transport http siteship https://app.siteship.ai/mcp

Codex

codex mcp add siteship --url https://app.siteship.ai/mcp

Then say: Get started with SiteShip.