AI Assistant
Connect the AI you already use — Claude, ChatGPT, or anything MCP-compatible — and manage your website by simply describing what you want.
Full disclosure: every page in this features section was written onto this site by an AI through this very connection.
Your website speaks MCP (the Model Context Protocol) — the open standard AI apps use to work with external tools. Connect your AI assistant once, and from then on "add a summer offer banner to the home page" is something you say in a chat, not a job for a content-management session.
The AI works with the same building blocks you'd use in the admin panel — heroes, feature grids, pricing tables, FAQs, galleries — so what it builds looks like it belongs on your site, follows your colours, and can always be fine-tuned by hand afterwards.
Image of a chat conversation asking the AI to update the website, with the finished page beside it.
Built to be trusted
An AI with write access to your website needs guard rails. These are them.
You approve the connection
Connecting uses the same secure OAuth flow as "Sign in with Google" — you log in, see exactly which site is being connected, and approve it yourself.
- No API keys to copy around or leak
- Each connection is scoped to one site
Every change is attributed
Edits made by the AI are recorded against the admin who approved the connection — the site history always says who, even when it was said in a chat.
- Same permissions as the approving admin
- No anonymous robot edits
Revocable in one click
See every connected AI app in your site settings and disconnect any of them instantly. Turning the feature off kills all connections at once.
- Connected apps listed in Website Settings
- The master switch is checked on every single request
Drafts before publishing
New pages are created as drafts — you (or the AI, when you tell it to) publish when the content is ready, not before.
- Preview before anything goes live
- Sensitive actions are designed to ask first
It knows your site's shape
The AI is offered tools matching the features your site actually has — and it learns your block styles, icons and colour system from the site itself.
- Pages, posts, menus, settings and media
- Thirty-plus block types with style guidance baked in
Rate-limited by design
Hourly limits on requests and writes keep even a confused AI from doing anything dramatic at volume.
- Separate budgets for reads, writes and image uploads
Connecting takes two minutes
Add the connector in your AI app
In Claude, ChatGPT or any MCP-capable app, add your website's connector address (it's shown in your site settings).
Approve the connection
Your browser opens the site's consent page. Log in with your normal admin account and confirm which site the AI may manage.
Start talking
That's it. Ask it to tidy a page, draft a post, or build something new — it has everything it needs.
Things you can just ask for
"Write a blog post announcing our new opening hours, and add it to the news page."
"Build a pricing section with our three packages and highlight the middle one."
"Add an FAQ to the services page answering the five questions customers always ring up about."
"Swap the hero image on the home page for the new one I just uploaded, and tighten up the headline."
The AI reads your existing pages first, so additions match the tone and structure of what's already there.
AI Assistant — common questions
Which AI apps can I use?
Anything that speaks MCP — Claude (desktop and web), ChatGPT, and a growing list of others. Because MCP is an open standard, you're not locked to one vendor: connect a different assistant tomorrow and it gets exactly the same tools.
Can the AI break my site?
It works within the same block system as the admin panel, so it can't produce broken layouts — and new pages arrive as drafts for you to review. Anything it edits can be edited right back; and you can disconnect it at any moment.
Does it see my customer data?
The AI only gets tools for the features enabled on your site, and every request is re-checked against your settings. Most content work — pages, posts, menus — touches no customer data at all. And the moment you disable the feature, every existing connection stops working.
Who is responsible for what it writes?
You are — which is why every change is attributed to the admin who connected it, drafts wait for review, and the consent screen makes it explicit which site you're handing the keys to. Treat it like a very fast assistant, not an unsupervised employee.
Do I need to be technical to set it up?
No. It's add the connector address, log in, click approve. If you can connect an app to your Google account, you can do this.
Proof, not promises
These feature pages — Bookings, Invoicing, Payments, Members and this one — were created end-to-end by an AI connected over MCP: pages created, every block placed, drafts left ready for review. The feature you're reading about is the feature that wrote it.
Explore more features: Bookings · Invoicing · Payments & Products · Members