Describe your website in chat — the connector builds it, checks the SEO, and publishes it to your own domain
The AI Website Builder is part of the same hosted MCP connector you use to run ads: paste one URL into Claude or ChatGPT, sign in with Google, and you can build and publish a full website by describing it in plain language.
Ask in plain English
›Build a five-page site for my dental clinic: home, services, about, a blog and a contact page with a map and hours — clean, modern, and fast.
›Show me a screenshot of the homepage on mobile, then make the hero headline shorter and move the appointment button above the fold.
›Add a blog and write three launch posts about teeth whitening, implants and check-ups, each with proper article structured data.
The assistant scaffolds a design toolkit (Tailwind, GSAP and designer fonts on a neutral starter), writes the pages, takes a screenshot to show you the result, stamps structured data on every page, and runs an SEO check that must pass before anything goes live. Every page ships 100% JSON-LD, and the built-in blog engine emits BlogPosting, Blog and Breadcrumb markup plus an RSS feed and a sitemap, so Google reads your blog as a blog. Pages are served statically from your own isolated hosting container, so the site is fast and there is no server process to run or patch. There is no code to write, no CMS to learn and no drag-and-drop dashboard. Anyone can spin up a free trial subdomain with no plan; a custom domain is added from your panel once you have an AI Server subscription.
What you can do
Build a whole site from a conversation
Tell the assistant what the site is for — a clinic, a law firm, a product launch — and it scaffolds the project, writes the pages and sections, and wires in the design toolkit. You review a screenshot of the live result at the viewport you ask for, request changes in plain language, and iterate until it is right. No local setup, no framework to learn, no build commands to memorize: the connector runs the build inside your hosting container for you.
Structured data on every page, checked before publish
This is not a nice-to-have here — it is enforced. Every page the builder produces ships 100% JSON-LD (Organization, WebSite, WebPage, and the right schema for each page type), and before anything goes live the toolkit stamps that markup and runs an SEO check that has to come back with zero errors. If a page is missing a title, a description or valid structured data, it does not publish until it is fixed. You get technically correct SEO as the default, not as a later project.
A blog Google actually recognizes as a blog
The built-in blog engine is database-less: posts are static files, but each one emits BlogPosting, Blog and BreadcrumbList JSON-LD, and the engine generates an RSS feed and a sitemap automatically. That is the combination search engines and AI answer engines look for when they decide whether a URL is an article worth surfacing. You write a post by describing it in chat; the structured data, feed and sitemap entry are produced with it.
Static hosting on your own isolated container
Your site is served as static files from a hosting container that is yours alone — fast to load, nothing to keep running, and no runtime server to be exploited or to fall over under traffic. The live site is exactly the files the connector publishes; there is no separate FTP client to configure and no deploy pipeline to maintain. Speed and uptime come from the architecture, not from a plugin you have to install.
A design toolkit, not a template you fight
The scaffold installs Tailwind for layout, GSAP for motion and a curated set of designer fonts on top of a neutral starter, so sites come out looking intentional rather than picked from a gallery. Because the assistant writes real files against a real toolkit, you can ask for a specific hero, a testimonial section, a pricing table or an animation and get it — the design bends to your brief instead of your brief bending to a theme's slots.
Your own domain when you are ready
Start on a free trial subdomain with no plan at all — describe a site, publish it, share the link the same afternoon. When you want it on your own domain, add an AI Server subscription from your panel under "Sunucum" and point the domain at your container. The site you built on the trial carries over; you are not rebuilding anything to go live properly.
Set it up in 60 seconds
- 1
Add the connector to Claude or ChatGPT
In Claude (claude.ai or Claude Desktop) open Settings → Connectors → Add custom connector and paste https://mcp.opus-growth.com/mcp. In ChatGPT, enable developer mode and add the same URL. Sign in with Google through hosted OAuth — about 60 seconds, with no API keys, tokens or server to set up.
- 2
Describe the site you want
Tell the assistant what the site is for and who it is for. It scaffolds the design toolkit and a neutral starter, writes the pages, then returns a screenshot of the live result so you can see it and ask for changes in plain language — copy, sections, layout, colors — until it matches your brief.
- 3
Approve, and it stamps SEO and publishes
When you are happy, the connector stamps structured data on every page and runs an SEO check that must pass with zero errors, then publishes the static files to your container. You get a live trial subdomain immediately; add an AI Server subscription from your panel to publish on your own custom domain.
Ask in plain English
›Build a five-page site for my dental clinic: home, services, about, a blog and a contact page with a map and hours — clean, modern, and fast.
›Show me a screenshot of the homepage on mobile, then make the hero headline shorter and move the appointment button above the fold.
›Add a blog and write three launch posts about teeth whitening, implants and check-ups, each with proper article structured data.
›Run the SEO check on every page and fix anything that fails before we publish — I want zero errors.
›Publish the site to my trial subdomain so I can share it, and tell me what I need to put it on my own domain.
›Add a testimonials section with three quotes and a subtle fade-in animation as the visitor scrolls to it.
Frequently asked questions
No. You describe the site in plain language in Claude or ChatGPT and the assistant does the building — it scaffolds the project, writes the actual page files, shows you a screenshot of the live result, and publishes it. There is no code for you to write, no CMS admin to learn and no drag-and-drop dashboard. If you can describe the site you want and react to a screenshot, you can build and publish it.
On your own isolated hosting container, served as static files. Static serving means pages load fast and there is no runtime server process to keep alive, patch or watch for crashes under traffic. The live site is exactly the files the connector publishes to your container — there is no separate upload step, FTP client or deploy pipeline to maintain.
Every page the builder produces ships 100% JSON-LD structured data, and before a site goes live the toolkit stamps that markup and runs an SEO check that must return zero errors. A page missing a title, description or valid structured data will not publish until it is corrected. The result is technically sound SEO by default, rather than something you bolt on months later.
Yes. The built-in blog engine is database-less — posts are static files — but each post emits BlogPosting, Blog and BreadcrumbList JSON-LD, and the engine generates an RSS feed and a sitemap automatically. That is exactly the signal search engines and AI answer engines use to recognize a URL as a genuine article, so your posts are positioned to be indexed and surfaced as blog content.
Anyone can create a free trial site on a subdomain with no plan at all — build it, publish it and share the link right away. To serve the site on your own custom domain you add an AI Server subscription from your panel under "Sunucum" and point your domain at your container. The site you built during the trial carries over, so going live is a switch, not a rebuild.
Yes — the same way you built it. Ask the assistant to change copy, add a section, swap an image, write a new blog post or restyle a page, and it edits the real files and republishes after the SEO check passes. Because everything lives as static files on your container, there is no lock-in to a proprietary page builder; the site is genuinely yours.
One URL and a Google sign-in, the same in both. In Claude open Settings → Connectors → Add custom connector and paste https://mcp.opus-growth.com/mcp; in ChatGPT enable developer mode and add the same URL. Authorization is hosted OAuth and takes about 60 seconds — no API keys, no tokens and no server to run. The same connector that builds your site also runs your ads across Google, Microsoft, TikTok and LinkedIn.
Explore more
Describe your site in chat and watch it get built, SEO-checked and published. Paste https://mcp.opus-growth.com/mcp into Claude or ChatGPT, sign in with Google, and spin up a free trial site on a subdomain with no plan — add an AI Server subscription from your panel when you are ready for your own domain.
