Build and publish websites from OpenClaw
Tell OpenClaw: “create a website for my small bike repair shop”. It builds the site and publishes it at a kleap.io link.
- Copy the command
openclaw skills install kleap - ConnectRun it in OpenClaw, then sign in on kleap.co when asked.
- Paste the promptThe tested prompt is just below. Change the studio for your business.
- Median time to a live link
- 8 min5 of 5 counted runs of our same-job test (a yoga studio site), OpenClaw 2026.4.15 with the Kleap skill, first word to the link
- Kleap's build itself
- 6 minmedian of the 5 builds inside those runs
openclaw skills install kleapChecked Oct 20, 2026
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.
5 of 5 counted runs reached a live link
No run was set aside. See every run
npx -y kleap-cli create with a brief the agent wrote itself.
No output until the build ended: the command blocks and prints once.
task completed, progress 100, neighborhood-bike-repair.kleap.io.
HTTP 200 from the live URL.
The replay is a real run of another job (Oct 18, 2026), so it shows a different site than the yoga job behind the medians on the left. Its own times are in the run below.
How do you connect Kleap to OpenClaw?
The skill is the shortest way in. MCP is there if you would rather give the agent the full tool list. Run live with OpenClaw 2026.4.15 and the ClawHub skill. The MCP route is from OpenClaw's docs.
Install, sign in once, ask.
Install the skill from ClawHub
The skill is published by the kleap owner on ClawHub. The command pulls it into the active workspace; add --global to install it for every workspace. It runs the Kleap CLI through npx, so Node must be available.
Terminalopenclaw skills install kleapYou should see: The skill appears in your workspace's skills. Add --global to install it for every workspace. We installed [email protected] this way.
Sign in once
Interactive machine: the command opens your browser and stores a token, nothing to paste. Headless server or CI: create a key at https://kleap.co/settings/api-key with the Full preset and expose it as KLEAP_API_KEY.
Interactivenpx -y kleap-cli auth loginHeadlessexport KLEAP_API_KEY=kleap_live_sk_...You should see: On a machine with a browser, a tab opens and a token is stored. On a server, KLEAP_API_KEY is set and nothing opens. Our run used the key.
Ask your agent
The skill tells the agent which commands to run: create, edit, publish, status, files, forms, analytics and domains. Creating or editing deploys by itself; files written directly need a publish afterwards.
You should see: The agent reads the skill, then runs one command such as kleap create. A site made by create or edit deploys by itself; files you write directly need a publish afterwards.
For the whole tool list, with OAuth.
Or add Kleap as an MCP server
OpenClaw can connect to a remote streamable-HTTP server. Add it, turn on OAuth in its config entry, sign in, then check it.
Terminalopenclaw mcp add kleap --url https://kleap.co/api/mcp --transport streamable-httpConfig entrymcp: { servers: { kleap: { url: "https://kleap.co/api/mcp", transport: "streamable-http", auth: "oauth", } } }Sign in and checkopenclaw mcp login kleap openclaw mcp doctor kleap --probeYou should see: openclaw mcp doctor kleap --probe reports the server reachable and lists its tools.
What can you ask OpenClaw to do with Kleap?
Copy one, change the details to yours. Each names what you want and what done looks like, then shows the Kleap tools it makes the agent call and what comes back.
Use Kleap to create a website for my small bike repair shop: services with prices, opening hours, a map section and a contact form. Wait for the build and send me the live URL.
- create_app
- check_task
- publish_app
What you get. This is the exact prompt of our real run: neighborhood-bike-repair.kleap.io. The skill uses kleap create, which does these calls for the agent and blocks until the build ends. The agent invented sample prices and hours because the prompt had none, and labelled them on the page.
task completed · form check passed · HTTP 200 · 1 credit charged. The whole run took 4 min 55 s, the build 3 min 44 s.
Read the Kleap site called Bike Repair, change the phone number in the header and the footer to the new one I give you, then publish and confirm it is live.
- read_files
- edit_files
- publish_app
What you get. The phone number changed in the header and the footer, republished, with proof it is live. Exact replacements, so no Kleap AI and no credits.
Pull the form submissions from my Kleap site since last night and message me a short list: name, request, how urgent.
- get_form_submissions
What you get. A short list of leads: name, request, urgency. The agent messages it to you; Kleap only supplies the data.
Give me last week's visitors and top pages for my Kleap site, and the three Google queries that bring the most impressions.
- get_analytics
- get_search_console
What you get. Last week's visitors and top pages, and the Google queries with the most impressions. Search Console needs to be connected to the site.
✓ 7d: 1 visitors, 6 pageviews — top: / (1), /#main (1), /#waitlist (1)
Does OpenClaw really get a site live on Kleap?
We ran the same job, on the same day, and kept every run.
5 of 5 counted runs reached a live link
Compare all agentsSame prompt for every agent on Oct 19–20, 2026, one build at a time. Median time to a live link: 8 min 29 s (first word to the link in the agent's last message); the shortest 6 min 01 s, the longest 9 min 36 s.
- Run 1: 8 min 29 s
- Run 2: 9 min 36 s
- Run 3: 6 min 01 s
- Run 4: 6 min 24 s
- Run 5: 9 min 07 s
In numbersOpenClaw and Kleap in numbers
Four measured figures from our runs, and what each one is.
- 3 min 44 sfor Kleap to build the bike repair site in our OpenClaw run, 1 credit. The whole run took 4 min 55 s
- 11 callsthe agent made: read the skill, one kleap create, eight polls, one curl. No error, no retry
- 1 commandinstalls the skill from ClawHub: openclaw skills install kleap
- 0 browserneeded on a server: set KLEAP_API_KEY and skip the login
Real runWhat did a real OpenClaw 2026.4.15 with the Kleap skill run look like?
Every call, in order, with the times we measured.
On Oct 18, 2026 we gave OpenClaw 2026.4.15 with the Kleap skill this job and kept every call. Here is what happened, with the times we measured.
- 40 sexec
The agent reads the skill first
After 34 s of OpenClaw start-up, the agent read the Kleap SKILL.md (6,078 characters). The skill tells it which command builds and publishes a site.
- 47 skleap create
One command does the whole job
npx -y kleap-cli create with a brief the agent wrote itself: sample prices, sample hours, a map placeholder and a form that saves enquiries, all labelled as provisional because the prompt gave no shop details.
- 50 s to 4 min 19 sprocess poll
It waits, politely
The command blocks until the build ends. The agent polled eight times with no output, which costs almost no context. Kleap's task started at 18:16:05 and completed at 18:19:49.
- 4 min 45 skleap create
Done, then checked on its own
One line came back: task completed, progress 100, the live URL. The agent then ran curl on that URL itself (HTTP 200) before it answered. Kleap's own form check had passed.
Neighborhood Bike Repair, live at neighborhood-bike-repair.kleap.io. Receipt: task completed · form check passed · HTTP 200 · 1 credit charged
| Client | OpenClaw 2026.4.15, Kleap skill 1.1.0 from ClawHub |
|---|---|
| Model | gpt-6.1-sol through OpenLux: OpenClaw needs some provider, the Kleap side is the same |
| Build task | 3 min 44 s (18:16:05 to 18:19:49 UTC) |
| Whole run | 4 min 55 s, 11 tool calls, no error, no retry |
| Cost | 1 credit charged for the build |
An OpenClaw agent read the Kleap skill, ran one CLI command, waited for the build and checked the live URL, in under five minutes with no error and no retry.
A real shop: the prompt gave no details, so the agent invented a name, sample prices and hours (labelled as samples on the page), and the map is a placeholder. Nobody submitted a real lead through the form.
Look insideWhat do the skill and its CLI look like, for real?
A real block of output, with the note that says what it is.
The frontmatter of the skill we installed (kleap 1.1.0 from ClawHub), then real commands run against production on Oct 18, 2026, copied as printed (the file list is shortened). This is all the agent has to read.
---
name: kleap
description: "Ship and run a live website or web app end-to-end — hosting, database, auth, forms/leads, analytics, custom domains — driven from this agent via the kleap CLI (npx, no install)."
version: 1.1.0
metadata:
openclaw:
requires:
bins:
- npx
primaryEnv: KLEAP_API_KEY
envVars:
- name: KLEAP_API_KEY
required: false
description: "kleap_live_sk_... API key (create it with the Full preset) for headless/CI use. Not needed if kleap auth login already ran once."
---
$ npx -y kleap-cli@latest create "<brief the agent wrote>" --json
kleap create --json: task task_afbe522b-715 app_create status=completed progress=100 app_id=120271 url=https://neighborhood-bike-repair.kleap.io
$ kleap status le-four-dore
✓ Le Four Doré (120173) — live: https://le-four-dore.kleap.io
$ kleap analytics kleap-cli --period 7d
✓ 7d: 1 visitors, 6 pageviews — top: / (1), /#main (1), /#waitlist (1)
$ kleap files ls le-four-dore
astro.config.mjs
package.json
public/robots.txt
src/components/KleapForm.tsx
src/layouts/Base.astro
…The first command is the one the OpenClaw agent ran: it blocks until the build ends, so the agent polled eight times and then read this single line. The analytics line is a real week of a brand-new site: one visitor. Nothing on this page claims traffic Kleap does not have.
Ask OpenClaw for a site and watch it go live.
What can't OpenClaw do with Kleap yet?
Every guide says what does not work, so you do not find out in the middle of a project.
Cron expressions, and a running Gateway
OpenClaw runs scheduled agent jobs from its Gateway with openclaw cron. Schedules are cron expressions, not plain English, and the Gateway has to be running when a job is due.
The skill needs Node and npx, and runs the latest CLI
It runs npx -y kleap-cli@latest, which resolved to 2.1.0 in our run. If your agent's environment has no Node, install it first or use the MCP server instead.
The agent decides the content
Our prompt gave no shop details and the agent did not ask: it invented a name, sample prices and hours, and put a visible notice on the page. The map section was a placeholder, not a real map. Give it your real details in the prompt.
Running npx needs an exec policy
The agent has to be allowed to run shell commands. In our isolated profile we allowed exec without prompts for that run; OpenClaw's finer per-command allowlist lives in its exec approvals file. Decide that policy deliberately.
VerificationWhat we verified for OpenClaw, and what we did not
Each claim is marked: we ran it, we read it in the docs, or we do not know.
Setup guides rot quietly. So each claim here is marked by how we know it. Runs last checked Oct 20, 2026; setup steps were verified on October 18, 2026 unless a line gives its own date.
We ran it
- A real OpenClaw run on Oct 18, 2026: OpenClaw 2026.4.15 with the Kleap skill 1.1.0 from ClawHub (installed with openclaw skills install kleap, accepted on the first try) built and published neighborhood-bike-repair.kleap.io from the prompt on this page. The model was gpt-6.1-sol through an OpenAI-compatible gateway, because OpenClaw needs some provider; the Kleap side is the same whatever model drives the agent.
- The Kleap CLI commands shown below, run against production. The outputs are copied as printed.
- Kleap's MCP server: initialize, tools/list (34 tools that day, 35 since Oct 19) and OAuth with dynamic client registration.
We read it in the docs
- The openclaw mcp, openclaw cron and exec-approval commands come from OpenClaw's documentation. We ran the embedded agent (openclaw agent --local), not the Gateway.
What if something doesn't work?
The failures we met, or the ones this setup is known to produce, with the fix.
The skill is installed but the agent does not use it
- Why:
- It was installed into one workspace and you are in another.
- Fix:
- Reinstall with --global, or install it in the workspace you are running. Name Kleap in the prompt.
I am not sure which install name to use
- Why:
- ClawHub lists the skill as kleap, owned by kleap. On OpenClaw 2026.4.15 the bare slug was accepted at the first try; we did not test the owner-scoped form.
- Fix:
- Run openclaw skills install kleap, and check the result with openclaw skills list.
The agent loses track on a long build
- Why:
- A small context window. The onboarding default of 16,000 tokens was too small for an agent with tools in our setup.
- Fix:
- Raise the provider's context window and max tokens in the OpenClaw config (we used 200,000 and 16,000) before you run the agent.
A headless server cannot sign in
- Why:
- The browser login has nowhere to open.
- Fix:
- Create a key at kleap.co/settings/api-key (Full preset, or narrower), set KLEAP_API_KEY, and skip kleap auth login.
I wrote files directly and the live site did not change
- Why:
- Files written with kleap files write are not deployed until you publish.
- Fix:
- Run kleap publish and wait for the verified-live line. kleap create and kleap edit deploy on their own.
What do people ask about OpenClaw and Kleap?
What is the Kleap skill on ClawHub?
A single skill that teaches an OpenClaw agent to run the Kleap CLI: create and edit sites, publish with the verified-live check, read files, forms and analytics, and manage domains. It needs npx and a Kleap sign-in.
Skill or MCP server in OpenClaw?
Start with the skill: it is one command and the CLI's compact output costs fewer tokens. Add the MCP server if you want the full tool list available directly, for example for a long-running agent.
Can OpenClaw run it on a server with no browser?
Yes. Create a Kleap API key with the Full preset, set KLEAP_API_KEY in the environment and skip the browser login. Use a narrower preset if the agent only needs to read.
Does the agent or Kleap write the site?
Both are possible. kleap create and kleap edit ask Kleap's AI to write the change. The files commands let your own model write exact file contents, which you then publish.
Is the Kleap skill safe to install?
Its source is open at github.com/kleaphq/cli in the clawhub/kleap folder. It runs the Kleap CLI and can only act on the Kleap account you sign in to. Read it before installing, as you should with any skill, and start with a Read-only key if you want to watch first.
How much does an OpenClaw-built site cost in Kleap usage?
In our run the build was charged 1 credit (Kleap's task log). The model that drives OpenClaw is billed by whoever provides it, not by Kleap. Exact edits written with kleap files commands run no Kleap AI. See the pricing page for what your Kleap plan includes.
What does the CLI actually print?
One to three lines. In our run kleap create printed a single line when the build ended: the task, status completed, the app id and the live URL. kleap status prints, for example: ✓ Le Four Doré (120173) — live: https://le-four-dore.kleap.io. The block above shows more real output.
Can OpenClaw run Kleap jobs while I sleep?
Yes, through openclaw cron, as long as the Gateway is running when the job is due. Use a key rather than the browser login, and the narrowest preset the job needs.
Official documentation: Kleap on ClawHub, MCP servers in OpenClaw (docs).
More about this setup
What it is, how it compares with the other ways in, and how to put it on a schedule.
In shortKleap + OpenClaw, in one paragraph
What it is and the three steps.
Install one skill from ClawHub. Your OpenClaw agent builds and publishes the site with one command, waits, and checks it is live. In our run the whole job took 4 minutes 55 seconds, no retry; Kleap's build took 3 min 44 s.
Connect
Paste the command or URL above into OpenClaw, then sign in on kleap.co.
Ask
Describe the site in plain words. The prompts below are ready to copy.
Live
Kleap builds and publishes, and reports it live only when the address answers.
Your optionsHow can OpenClaw reach Kleap: skill, MCP server or plain shell?
Alone, in the app, or with Kleap, side by side.
OpenClaw can reach Kleap three ways. They all reach the same account and the same sites.
- We ran it
The ClawHub skill
- One install command. It runs the Kleap CLI through npx, so Node must be available.
- In our run the agent read the skill, made one kleap create call and polled it: the command blocks and prints a single line when the build ends.
- The source is open: read it before you install it, as you should with any skill.
Best for most OpenClaw users.
- From OpenClaw's docs
The MCP server
- openclaw mcp add kleap with OAuth gives the agent all 35 tools in-process.
- More surface than most jobs need, which costs context.
- Worth it for a long-running agent that does many different things.
Best when the agent needs everything, from files to domains.
- DIY
Plain shell, no skill
- npx -y kleap-cli works from any shell. You write the instructions yourself.
- No skill means the agent has to learn the order of calls on its own.
- Useful in cron and CI where there is no agent at all.
Best for scheduled scripts without an agent.
Our take. Use the skill unless you know you need the whole tool list. If you later do, add the MCP server next to it.
SEO on a scheduleCan OpenClaw run the SEO work every day?
A scheduled prompt, and what we ran ourselves.
OpenClaw runs scheduled agent jobs from its Gateway (openclaw cron, also called automations). Schedules use cron expressions rather than plain English, and the Gateway has to be running when a job is due. Create an agent job with the prompt below.
Every morning, for each of my Kleap sites: read get_search_console, improve the one page that deserves it with edit_files, publish_app and confirm with get_publish_status, then send me what changed. Never invent statistics, never change the design, touch at most two pages per site.
Google Search Console must be connected to the site for the search data. If it is not, Kleap hands the agent a consent link for you to open. The full step-by-step prompt lives on the hub.
We ran this loop for real with Claude Code and the Grok CLI on a test site. We did not run it with OpenClaw, so run it once by hand and read the result before you schedule it.
More from Kleap
Pages on the rest of the site that pair with this guide.
Using another agent? Same Kleap account, same sites. Compare the seven agent guides.
Put OpenClaw to work on your website
Connect once, then ask in plain words. Kleap builds, hosts and publishes, and your agent keeps the site improving.
