Skip to content

Claude & AI

Claude builds your website – and then helps run it.

Connect Claude to Kaleta and ask for whole pages, a new look or a quick fix. Your team can hand it requests through Ask Claude, and it can do the weekly chores on a schedule. Claude saves its work as drafts with a preview link, stays inside the limits you set, and a whole session can be undone in one step.

What you can ask

Real requests, real results.

Claude reads your site first – pages, design system, shared classes – so it builds with your look instead of inventing one.

“Build a site for Novak Plumbing in Leeds: home, services, prices and a contact page with an enquiry form. Navy and orange.”

Pages built from ready-made sections and your design system, saved as drafts, with a preview link.

“Turn this HTML export of our old homepage into a Kaleta page.”

The HTML becomes editable builder sections; its styles become shared classes.

“Make every section heading use the same style and tighten the spacing on phones.”

One shared class changed – the whole site follows.

“We’re closed from 24 to 26 December. Put it on the site.”

An exception in the opening hours – the notice bar, the structured data and Google Business Profile follow. On a drafts-only connection Claude proposes the exception and a person applies it in Business details.

“Move our WordPress site here and keep the old addresses working.”

Claude runs the WordPress import in resumable batches – menus, WooCommerce products and Polylang or WPML languages too – everything hidden, with permanent redirects from every old address.

“Go through this week’s enquiries and draft replies.”

Each enquiry gets a kind, a priority and a drafted reply. Nothing is sent – a person decides.

How it works

From a request to a published page.

01

You ask.

In the Claude app or Claude Code, in plain language.

02

Claude looks.

It reads your pages, the design system and the building blocks it may use.

03

It builds a draft.

Page builds, site parts and news are saved as drafts – visitors still see the published site.

04

You preview.

Claude sends a signed preview link that works for a limited time, even without signing in.

05

You say “publish”.

Claude publishes only when you tell it to, and only if your account may publish.

Claude on staff

More than a builder: an operator with limits.

Once the site is live, Claude keeps it current – for the whole team, on a schedule if you like, and always in a way you can check and take back.

Read the guide

Requests from staff.

Colleagues write what they need in Ask Claude – on the dashboard or under Claude → Ask Claude, with attachments. Claude does it as drafts and answers with a note and links; the requester gets an e-mail, and the result waits in Waiting for you on the dashboard.

Comments on drafts.

A shared preview takes comments on single elements – no account needed. Claude reads them and fixes the draft.

Guardrails.

An hourly change limit, protected pages and no deleting – set in Claude settings, for every connection, whatever its access.

Every change says why.

Each change carries its reason in the change log. A notebook keeps decisions and wording rules for the next session.

Undo a session.

Claude settings → Claude sessions puts back everything one session changed. Rows people edited since are left alone unless you say otherwise.

Scheduled runs.

A weekly review, a monthly report, daily triage. The site keeps the schedule, a Claude routine does the work as drafts, and a missed run raises an alert.

Advanced: start from a design

Design the look first. Claude builds the site from it.

Rather settle the look and feel before a single page exists? Shape it in Claude Design, then hand it to a Claude session connected to your Kaleta site. From that point Claude works inside Kaleta – with your design as its brief.

01

Design it in Claude Design.

Try colours, type, spacing and a page or two until the site looks and feels the way you want.

02

Hand it over.

Export the design and give it to Claude in a session connected to your site – in the Claude app or in Claude Code.

03

Claude sets up the look.

Colours, fonts and corner radius go into the design system, brand fonts into Media, and the styles of the design become shared classes.

04

…and builds the pages.

Your mock-ups become editable builder sections, saved as drafts with a preview link. From there it is an ordinary Kaleta site – edit it in the builder or keep asking Claude.

“Here is our design from Claude Design. Put its colours and fonts into the design system, then build the home page and a services page from it.”

Design tokens set right away, the pages as drafts with a preview link – and every page Claude adds later follows the same look.

“Now add a pricing page and a contact page with an enquiry form, in the same style.”

New pages built from your design system and shared classes, not from a fresh guess.

Tip: design tokens in the W3C format can also be imported in the admin, under Appearance → Site appearance → Import and export.

What Claude can change

Drafts, direct changes and things it never touches.

The connection has the permissions of the account that approved it, or less – drafts only or read only. Every change Claude makes is recorded in the change log in the admin.

As a draft with a preview.

  • Page builds
  • Header, footer and other site parts
  • News
  • The item page of collections
  • Colours, fonts, shared classes and menus – as one draft look you preview on the whole site
  • New pages and collection items start hidden
  • On a drafts-only connection also proposed exceptions to the opening hours and triage suggestions on enquiries – a person applies them; everything waiting shows up in Waiting for you

Right away.

  • New shared classes
  • Site name, description and company details
  • Redirects
  • Collections and their items
  • Moving pages, news items and collection items to the trash (restorable for 30 days)
  • Deleting media, pop-ups or categories – only when you ask, and never when the guardrails rule out deleting

Never over the connection.

  • The site email and mail settings
  • Webhooks, connection credentials and newsletter keys
  • Backups and updates
  • Users, roles and security settings
  • The subscriber list, whistleblowing reports and statistics about individual visitors – a personal data request for one e-mail address (administrators only) shows and erases its subscription
  • PHP code of the site and add-ons

Safety net: a whole Claude session can be undone in one step, the last 20 published versions of every page stay in its history, deleted pages, news items and collection items stay in the trash for 30 days, and you can disconnect Claude at any time in My account.

Setup

Connect in two minutes. No keys to paste.

01

Check the feature.

New installations have the Claude connection on. On older sites open Administration → Features and switch on Claude connection (MCP). Claude settings then shows your site’s exact address.

02

Add the connector.

In the Claude app open Settings → Connectors → Add custom connector and enter https://your-site.com/mcp.

03

Approve access.

Claude sends you to your own site to sign in and allow access. A new connection starts as Drafts only – you publish; allow publishing there when you want to. Disconnect any time in My account.

Before you start

  • Your site runs on HTTPS – at the root of its domain or in a subfolder.
  • A Claude plan that lets you add custom connectors.
  • Prefer the terminal? In Claude Code run claude mcp add --transport http kaleta https://your-site.com/mcp and confirm access in the browser.
  • A new connection lists the Essentials – 36 core tools – so every conversation starts lighter, and Claude finds the other hundred tools when a task needs them. Pick All tools when you connect or later in My account.
  • The Kaleta plugin for Claude adds five ready skills: move from WordPress, launch a site, weekly care, set up bookings and a compliance check. It is in the repository under integrations/claude-plugin.

Security of the connection

Your site, your sign-in, your rules.

Claude never gets your password or an API key. You approve access on your own site, the same way you sign in to the admin, and you can take it back at any moment.

Claude connection

sign-in

OAuth 2.1 with PKCE

access

expires after an hour

permissions

the approving account’s, or less

revoke

My account → Connected apps

stays connected

a year from last use

secrets to copy

none

Two kinds of AI

Claude builds. The assistant helps you write.

Claude over MCP.

Builds and edits the whole site from a conversation in the Claude app or Claude Code. Uses your Claude subscription; Kaleta only receives the requests it sends.

Writing assistant (your own key).

Rewrites, shortens and proofreads texts, suggests headlines and SEO descriptions, and drafts sections. Pick Anthropic Claude, OpenAI, Google Gemini or Mistral and add your own API key; text is sent only when you click an assistant button.

FAQ

Questions people ask.

Can Claude see my visitors’ data?

Only enquiries from your forms and bookings, and only when the account that approved the connection may open them. Claude reads them when you ask – for example to sum up this week’s enquiries – and every read is recorded in the change log. The subscriber list, whistleblowing reports and statistics about individual visitors are never available over the connection; a personal data request for one e-mail address (administrators only) shows whether it has a subscription and can erase it.

Does it cost anything?

Kaleta is free and open source. Using Claude requires your own Claude plan from Anthropic.

Can Claude break my site?

Page builds, site parts and news are drafts until you publish them, and so are changes of the look. Guardrails in Claude settings can limit changes per hour, protect pages and rule out deleting. If a session still goes wrong, Claude settings → Claude sessions puts back everything it changed in one step.

Can Claude work on a schedule?

Yes, with a routine in the Claude app or Claude Code. The site keeps the schedules (weekly review, monthly report, enquiry triage, staff requests or your own task); the routine asks what is due, does it as drafts and reports back. A missed run raises an alert.

Which Claude do I need?

The Claude app with a plan that supports custom connectors, or Claude Code. Your Kaleta site must run on HTTPS.

Can I use other AI tools?

The connection uses MCP, an open standard, and signs in with OAuth. Kaleta is tested with Claude; other MCP clients that support OAuth may work too.

Can Claude publish on its own?

Claude publishes only when you tell it to, and only if the connection may publish. A new connection starts as Drafts only – you publish, and a drafts-only connection never can – the work waits for someone who may, in Waiting for you on the dashboard.

Let Claude build your next site.

Download Kaleta, connect Claude and describe the site you need.