Can Claude build a website? Yes, in under two minutes. To put it online it needs a hosting tool

What did we test?

One job, the same one we use for the success-rate runs of the agents on our AI agents page: a website for a yoga studio with a class schedule, teachers, pricing and a booking request form, in calm colours. We ran it in Claude Code, Anthropic's coding agent, because it is the Claude client that works on files in a folder on your computer.

That last row matters. This test measures what Claude does with no way to publish. What Claude does with a terminal and a hosting login we did not test: in run 3 it offered to publish with them, and that is the second route below.

What did Claude build on its own?

The page is good. Claude chose a sage, sand and cream palette, serif headings, a weekly schedule, teacher profiles, prices and a booking form, and the pages have a mobile menu. If you are judging Claude on the look of a first draft, it passes.

What was missing in all three runs

1. No live link. The task said “Publish it and send me the link.” Run 1: “I built the site, but it isn't published and I haven't sent you a link.” Runs 2 and 3: “I built the site, but I couldn't publish it or send you a link.”
2. Everything was made up. All 3 named the studio “Stillwater Yoga” and invented the teachers, times, prices, address and e-mail. All 3 said so. Run 1: “Everything is made up.”
3. The booking form didn't reach the studio. One form only worked on one host (Netlify Forms). The other two opened the visitor's own e-mail app with a request addressed to a placeholder address.
4. Claude never looked at its own result. Runs 1 and 2 said they had not opened the page. With file tools only, Claude could not.

“Alternatively, if you give me a terminal and a hosting account (Netlify, Vercel or GitHub Pages), I can publish it for you.”

All 3 runs also told us how to finish the job ourselves: drag the folder onto Netlify Drop, a drag-and-drop static host. We did not run that step, so we don't vouch for it. We mention it because it shows where Claude's work ends: at a folder of files.

Why can't Claude publish a website by itself?

A website is a folder of files plus a computer that answers requests for it at an address, over HTTPS. Claude writes the files. A hosting service, or a server of your own, provides the computer and the address, and Claude can only use the tools it has been handed. In our runs the only tools were file tools, so Run 1 answered “I have no hosting or deploy access and no email tool in this session”. That is a limit of the setup, not of the model: in run 3 Claude itself offered to publish if it were given a terminal and a hosting account.

Two other gaps have a different cause. Claude does not know your studio, so it invented details unless you supply them. And a form has nowhere to send submissions until someone gives it a destination: you, or a service that stores them.

How can you get a Claude-built website online? Three routes

Pick the first for a throwaway preview, the second if the code is the product and you already run your own deployment, and the third if the goal is a site that exists at an address by the end of the conversation.

How do you build and publish a site with Claude and Kleap?

Kleap is a website builder that Claude can operate. It builds the site, hosts it on a kleap.io address (or your own domain), stores the form submissions and checks that the published address answers. Setup is a connector you add to Claude.

1. Connect Kleap to Claude. In Claude on the web or desktop, open Customize, then Connectors, add a custom connector and paste the URL below, then sign in to Kleap (on Team and Enterprise plans an owner adds it in Organization settings first). In Claude Code, run the command below, then /mcp to sign in.
2. Paste a prompt with your real details. Name, services, prices, opening hours and the e-mail that should get leads. We use the prompt below, which ends with a sentence that asks Claude to wait for the build. It is not a guarantee: one of our five counted runs published early anyway, as the results show.
3. Let Claude wait. Kleap's build took 4 min 34 s to 6 min 14 s in the runs that worked. In the runs that worked, Claude checked the task's status two to five times.
4. Check the link yourself. Claude publishes and reports the address. Open it, then send a test through the form.
5. Change things in words. Ask Claude for the change you want on the live site and have it republish. In our portfolio run Claude made two edits this way and republished.

https://kleap.co/api/mcp

claude mcp add --transport http --scope user kleap https://kleap.co/api/mcp

Use Kleap to build a website for my yoga studio: class schedule, teachers, pricing and a booking request form. Calm colours. Wait for the build to finish, publish it and send me the link.

How well did Claude plus Kleap work in our runs?

4 of 5 counted runs ended with a live link to a finished site. Among those 4 the median time was 7 min 10 s (fastest 7 min 00 s, slowest 8 min 59 s). That is about 4 times the median Claude alone needed (1 min 44 s), because Kleap's build is the longest part. It is also the difference between a folder of files and a site with an address.

The one failure is worth knowing about. In that run Claude published and announced the site while Kleap's build was still going. The link answered 200, but the site was half built, so we counted the run as a failure. Our prompt asks Claude to wait for the build to finish, which is not a guarantee. Here is what happened without that sentence:

Three runs are too few to promise a rate, so read that table as a warning, not a statistic: say “wait”, and open the link before you share it.

How do you get a better first site out of Claude?

What we saw suggests three habits.

• Give the real facts in the first message. Every closing message in our Claude-alone runs listed the missing facts as placeholders. Put the name, what you offer, the prices, the hours and the contact e-mail in the prompt and there is less to swap afterwards.
• Say where leads go. A booking form needs a destination. Name the address, or ask for a form that stores submissions you can read back.
• Ask it to wait, then verify. “Wait for the build to finish, publish it and send me the link”, then open the link on your phone.

What should you check before you share the link?

• No placeholder left: search the page for the studio name, the teachers, the prices and the address Claude invented.
• Submit the form yourself and confirm the message reaches you. In our Claude-alone runs the forms were set up in ways that would not have reached the owner as written.
• Open the address on a phone and in a private window, signed out of everything.
• Click through the footer and the menu links.

When is this route not the right one?

• You want the code in your own repository and your own deployment. Use Claude Code with your hosting (route 2). A hosted builder serves the site from its own platform.
• You only need a visual draft to react to. Claude alone, in about two minutes, is faster and enough.
• You need the result in the next minute. Kleap's build takes minutes, not seconds.