Build a website with ChatGPT
Tell ChatGPT: “build a website for my yoga studio”. It builds the site and publishes it at a kleap.io link.
- Copy the server URL
https://kleap.co/api/mcp - ConnectRun it in ChatGPT, 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
- 6 minMeasured with Codex, OpenAI's agent, not ChatGPT5 of 5 counted runs of our same-job test (a yoga studio site), Codex CLI 0.163.0, first word to the link
- Kleap's build itself
- 4 minmedian of the 5 builds inside those runs
https://kleap.co/api/mcpChecked 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 (Codex's runs, not ChatGPT's)
No run was set aside. See every run
This is Codex, OpenAI's agent, not ChatGPT. ChatGPT cannot be driven from a script, so the run below is the closest thing we could record.
Build started, app 120500, task id and build link returned.
Polled about once a minute: progress 34, 34, 34, 43, 43, then completed.
status published, still-yoga.kleap.io.
Name Still Yoga, live address confirmed.
The replay is a real run of the yoga job (Oct 19, 2026); its own times differ from the medians on the left, which cover every counted run of the same job.
How do you connect Kleap to ChatGPT?
Kleap is not in ChatGPT's app directory yet, so you add it as a custom MCP server. You sign in to Kleap in your browser; there is no key to copy. Kleap is not in ChatGPT's app directory yet, so you add it yourself: a short setup with a sign-in in your browser.
Four steps. Steps 2 and 3 happen in ChatGPT and in your browser; nothing is installed on your computer.
Copy Kleap's connector URL
This is Kleap's remote MCP server. It speaks OAuth with dynamic client registration, so you never enter a client ID or a secret.
Server URLhttps://kleap.co/api/mcpYou should see: The URL is in your clipboard. Nothing is created yet.
Add it as a custom MCP server
In ChatGPT on the web, open Plugins (chatgpt.com/plugins), click the plus button and choose Add custom MCP server. Name it Kleap, paste the URL as the Server URL, choose OAuth for authentication, accept the risk warning and click Create as a plugin. Then install it from your personal plugins before you use it in a conversation.
You should see: A plugin named Kleap appears in your personal plugins, with OAuth as its authentication.
Sign in to Kleap and approve
ChatGPT opens kleap.co. Sign in, or create a free account, and approve access. The agent can only ever touch your own Kleap sites, and you can revoke it later from your Kleap settings.
You should see: Kleap's consent screen lists the seven permissions the agent will get, with an Approve and a Deny button. Pick Approve.
Ask for a site
Start a new chat, make sure the Kleap plugin is enabled for it, and describe what you want. A first build takes several minutes; ChatGPT follows the build task and comes back with the live link.
You should see: ChatGPT calls create_app, then check_task until the build is done. Expect several minutes, and a link to Kleap's build page while you wait.
What can you ask ChatGPT 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 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.
- create_app
- check_task
- publish_app
What you get. A live one-page site on a kleap.io address. This is the prompt Codex ran in the replay above: 5 min 34 s from the first word to the live link.
status published · live address answers 200 · 1 credit charged. Kleap built it in 4 min 14 s, the whole Codex run took 5 min 34 s.
Find my Kleap site called Bakery. Change the hero headline to "Roasted slow, baked fresh" and add Saturday opening hours, 8:00 to 14:00. Publish it and confirm it is live.
- find_app
- read_files
- edit_files
- publish_app
What you get. A republished page. On Kleap's side the read takes about 0.6 s, the edit 0.7 s and the publish about 27 s, because publish waits until the new version serves.
Use Kleap to check how my site did in Google Search over the last 28 days. Take the page with the most impressions and the weakest click-through rate, rewrite its title and meta description for the query people actually use, publish it and tell me what you changed.
- get_search_console
- read_files
- edit_files
- publish_app
What you get. A rewritten title and description for the page that deserves it. Needs Search Console connected to the site; if it is not, Kleap hands ChatGPT a consent link for you to open.
connected: false · clicks 0 · impressions 0Google Search Console isn't connected for this site. The owner connects it from the site's options in Kleap (Integrations → Search Console).
Show me the contact form submissions my Kleap site received since last Monday, newest first, and draft a short reply to each one.
- get_form_submissions
What you get. The submissions, newest first, with the fields each form collected. ChatGPT drafts the replies; Kleap does not send e-mail for you.
Search for available domain names for my bakery and give me the payment link for the best .com. Do not buy anything yourself.
- search_domains
- check_domain
- buy_domain
What you get. A short list of available names and a payment link you pay yourself. Nothing is bought without you.
· lyonbakery.com taken✓ lyonbakery.fr available✓ lyonbakery.io availableBuying returns a payment link that you pay yourself.
Does ChatGPT 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, with Codex CLI 0.163.0
Compare all agentsChatGPT cannot be driven from a script, so we ran the OpenAI agent that can: Codex CLI, OpenAI's own coding agent, on the same job. These are Codex's runs, not ChatGPT's. Same prompt for every agent on Oct 19–20, 2026, one build at a time. Median time to a live link: 5 min 50 s (first word to the link in the agent's last message); the shortest 5 min 34 s, the longest 8 min 16 s.
- Run 1: 5 min 34 s
- Run 2: 5 min 47 s
- Run 3: 5 min 50 s
- Run 4: 5 min 58 s
- Run 5: 8 min 16 s
Without “Wait for the build to finish” in the prompt: 3 of 3 (tiny sample) after Kleap changed its first answer. The prompts on this page include the sentence anyway.
In numbersChatGPT and Kleap in numbers
Four measured figures from our runs, and what each one is.
- 3 of 3runs of OpenAI's own agent, Codex, reached a live site on Kleap from one sentence. ChatGPT itself was not run: it cannot be scripted
- 5 min 47 smedian from the first word to the live link in those three runs; Kleap's build alone took about 4 minutes
- 1 creditcharged for the build. ChatGPT's own plan is billed by OpenAI
- 35 toolsChatGPT can call: build, edit, publish, leads, traffic, domains
Real runWhat did OpenAI's own agent do with the same job?
Every call, in order, with the times we measured.
ChatGPT itself cannot be driven from a script, so we gave the job to Codex CLI, OpenAI's coding agent, and kept every call. This is what happened, with the times we measured. It is Codex, not ChatGPT: the Kleap side of the job is the same.
- 0 to 31 screate_app
Codex reads first, then calls Kleap
Codex opened OpenAI's own Sites skill (it ships inside Codex) and read it, then did what the prompt said and used Kleap. It wrote the brief itself: sage green and ivory, clearly labelled sample details, bookings sent to the Kleap dashboard.
- 45 s to 5 min 17 scheck_task
It waits, because the prompt told it to
Six polls about a minute apart, with a one-line status after each (progress 34, 34, 34, 43, 43, completed). A prompt without the wait sentence ended earlier, see the success rates.
- 5 min 17 sget_publish_status
Kleap had already published
A build on Kleap publishes the site when it completes (published_at 23:35:26 UTC, one second before the task closed). Codex checked the status rather than publishing a second time.
- 5 min 34 sget_app
A link and the caveats
The reply gives the live address and says the studio details are samples and that delivery of a real booking request was not tested.
Still Yoga, live at still-yoga.kleap.io. Receipt: status published · live address answers 200 · 1 credit charged
| Client | Codex CLI 0.163.0, OpenAI's own agent, model gpt-6-astra, with a Kleap API key |
|---|---|
| Build task | 4 min 14 s (23:31:13 to 23:35:27 UTC) |
| Whole run | 5 min 34 s, 9 Kleap calls, none failed |
| Cost | 1 credit charged for the build |
| Setup | A clean Codex profile (login only, none of our skills), Kleap added with two -c flags |
OpenAI's own agent, started with one sentence and a Kleap key, built, waited for and verified a live site on Kleap, with no retry and no error.
That ChatGPT itself did this: Codex is OpenAI's coding agent, not ChatGPT, and ChatGPT cannot be driven from a script. The studio name, schedule and prices are sample content, labelled on the page, and nobody submitted a real booking request.
Ask ChatGPT for a site and watch it go live.
What can't ChatGPT do with Kleap yet?
Every guide says what does not work, so you do not find out in the middle of a project.
Custom connector, not a directory app
Kleap is not in ChatGPT's app directory yet, so you add it yourself. Which plans can add a custom MCP server is OpenAI's decision, and inside a workspace your admin's.
Builds take minutes
Kleap's build took about 4 minutes in our Codex runs and the whole job a little under 6. create_app returns a task in about 3 seconds so ChatGPT is never stuck waiting; a bigger brief takes longer. If a chat goes quiet, send: Check my Kleap build.
It only touches your own sites
The connector is scoped to your Kleap account. ChatGPT cannot see anyone else's sites and cannot buy anything: a domain purchase is a payment link you pay.
Scheduled runs depend on OpenAI
OpenAI decides which connectors a scheduled task can use and when it pauses to ask for approval. Run the SEO prompt once by hand and read the result before you schedule it.
VerificationWhat we verified for ChatGPT, 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
- Kleap's MCP server answers initialize, tools/list and OAuth discovery on Oct 18, 2026 (34 tools that day, 35 since seo_audit shipped).
- Three runs of Codex CLI 0.163.0, OpenAI's own agent, on Oct 19, 2026: one sentence in, a live link out, 3 of 3 times (5 min 34 s to 5 min 50 s). This is Codex, not ChatGPT.
- A script client sending the same calls on Oct 18, 2026 (a one-page bakery, verified live in 4 min 36 s).
We read it in the docs
- ChatGPT's own screens (Plugins, Add custom MCP server, OAuth, enabling the plugin in a chat) are taken from OpenAI's custom MCP guide. OpenAI has renamed that screen more than once and we did not re-run it for this page, which is why the steps name what to look for rather than where to click.
What if something doesn't work?
The failures we met, or the ones this setup is known to produce, with the fix.
Kleap does not appear in my chat
- Why:
- The plugin exists but was not installed from your personal plugins, or is not enabled for this conversation.
- Fix:
- Install it from your plugins, start a new chat and enable Kleap for it before you write the prompt.
ChatGPT cannot reach the server or the sign-in loops
- Why:
- The URL was altered, or OAuth was not chosen as the authentication method.
- Fix:
- Use exactly https://kleap.co/api/mcp as the Server URL and choose OAuth. Kleap publishes its OAuth discovery document, so there is no client ID to enter.
The build looks stuck
- Why:
- The first build of a site takes minutes and ChatGPT only reports when it asks.
- Fix:
- Ask it to check the build. It calls check_task, and the kleap.co/build link in its first answer shows progress without ChatGPT.
It says it published but the page looks the same
- Why:
- A cached tab, or the publish did not finish.
- Fix:
- Ask for get_publish_status. Kleap only reports published once the new version is answering at its address, and returns the audit with it.
What do people ask about ChatGPT and Kleap?
Can ChatGPT build a website?
On its own ChatGPT writes code, but nothing hosts it. With Kleap connected it asks Kleap to build the site, host it on a kleap.io address or your own domain, and publish it. Kleap reports the site as live only once it is actually serving.
Do I need an API key?
No. The connector signs you in with OAuth in your browser, so there is nothing to copy. ChatGPT's custom MCP screen offers OAuth, so you will not meet a key field. An API key (kleap_live_sk_…, created at https://kleap.co/settings/api-key) is only for unattended jobs, scripts and clients that cannot open a browser. Pick the narrowest preset: Read-only to inspect sites, Build to change and publish them.
Is Kleap in the ChatGPT app directory?
Not yet. For now you add it yourself as a custom MCP server with the URL on this page. Your Kleap account and sites stay the same either way.
Which ChatGPT plan do I need?
OpenAI controls who can add custom MCP servers, and the menu has changed names several times. Check OpenAI's guide linked below for your plan. In a Business or Enterprise workspace, an admin may have to allow it.
Can ChatGPT edit a site I already built in Kleap?
Yes. It lists your sites or finds one by name or address, reads the files, changes only what must change, then republishes. You can also describe the outcome and let Kleap's AI write the change.
Does it cost anything to connect Kleap?
Connecting is free. Building and AI edits draw on your Kleap usage: every build we recorded was charged 1 credit, and the free plan includes some usage. If your agent writes the files itself with write_files or edit_files, Kleap does not run its own AI for that step. Publishing on a Kleap address is free. ChatGPT's own plan is billed by OpenAI, not by Kleap. See the pricing page for what each plan includes.
How long does it take ChatGPT to build a website with Kleap?
Several minutes. In our three runs of OpenAI's Codex agent, a one-page yoga studio site took between 5 min 34 s and 5 min 50 s from the first word to the live link, of which Kleap's build was about 4 minutes. A site with many pages takes longer. The first call returns within seconds and ChatGPT checks back, so the chat is never blocked.
What can ChatGPT not do with Kleap?
It cannot see anyone else's sites, and it cannot spend your money: a domain or a plan upgrade is a payment link that only you can open and pay. It also cannot send e-mail: it can read your leads and draft replies, and you send them.
Is it safe to approve the connection?
The consent screen lists exactly what the agent gets: read and create apps, edit and publish them, send prompts to Kleap's AI, check task status, read form submissions and read analytics. You can revoke access later from your Kleap settings.
Official documentation: Add a custom MCP server in ChatGPT (OpenAI).
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 + ChatGPT, in one paragraph
What it is and the three steps.
Describe the site in ChatGPT. Kleap builds it, hosts it on a real address, and tells ChatGPT whether it is actually live. We could not script ChatGPT itself, so the proof is OpenAI's own agent, Codex: it reached a live site in 3 runs out of 3.
Connect
Paste the command or URL above into ChatGPT, 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 ChatGPT build you a website?
Alone, in the app, or with Kleap, side by side.
They are not equal, and the honest answer depends on what you want after the first page exists.
- Free, no account
ChatGPT writes the code, you host it
- You get files, not a site. Hosting, a domain, SSL and a way to receive form submissions are still yours to set up.
- Every edit means pasting new code over old code.
- Nothing checks that the page works once it is online.
Best for a one-off static page you already know how to host.
- You leave ChatGPT
A builder with its own chat inside
- You work in the builder's editor, which is good if you like clicking and dragging.
- ChatGPT is no longer in the loop, so it cannot run SEO passes or summarize leads for you afterwards.
- Another tool to learn, another login.
Best if you want an editor and not an agent.
- What this page sets up
ChatGPT drives a hosted builder (Kleap)
- One sentence in, a live address out. Hosting, SSL and forms are included.
- ChatGPT keeps working on the site: edits, publishes, reads leads and traffic, proposes SEO changes.
- A publish is reported done only once the address answers.
Honest limits: a custom connector for now, and a first build takes minutes.
Our take. Choose the third if you want ChatGPT to stay your control panel after launch. If all you need is a file, the first is enough.
SEO on a scheduleCan ChatGPT run the SEO work every day?
A scheduled prompt, and what we ran ourselves.
ChatGPT can run a prompt on a schedule (scheduled tasks). Create a task, paste the prompt below and pick a time. OpenAI decides which connectors a scheduled run may use, and it can pause to ask you to approve actions that change data. Run the task once by hand and read the result before you rely on it.
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 ChatGPT, 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.
- AI website builderWhat Kleap builds when ChatGPT is not involved
- Bakery website exampleAnother kind of site agents build: a one-page bakery
- Connect a domain you ownMove from a kleap.io address to your own
- Can ChatGPT build a website? TestedWhat OpenAI's agent does alone, and the three ways to get a live link
- MCP, CLI and skills referenceEvery tool and every way in
Using another agent? Same Kleap account, same sites. Compare the seven agent guides.
Put ChatGPT to work on your website
Connect once, then ask in plain words. Kleap builds, hosts and publishes, and your agent keeps the site improving.
