Connections — MCP

Let Claude, Cursor or Codex build pages — as real blocks, not pasted HTML

The tools you already work with — Claude, Cursor, Codex — speak one protocol for talking to a program that is not their own. This site speaks it too. They do not get HTML that has to be translated back: they work on the same tree the editor works on, so what they build, you open and change like anything else.

What a tool may do

List the pages and posts of the site
Read a page and its whole layout
Read the block catalogue and the design system
List your images and use them by id
With a writing key: save a layout, or create a draft page

What no key can do

No users, no roles, no passwords
No orders, no customers, no invoices
No settings, no plugins, no files
No mail, no newsletter, no export
Not switched off — simply not there

How it stays yours

The door is shut until you open it
One key per tool, shown once, revoked with one tick
Read only, or read and change — you decide per key
Blocks this site does not know are thrown away on the way in
Every change is a version you can take back in the editor

Blocks, not HTML

What comes back is the page, not a copy of it.

A tool that writes HTML into a page leaves you with a page you cannot edit: one block with markup in it, and the builder can do nothing with it. Here the tool reads the block catalogue and the design system first and answers in the same tree the editor works on — sections, grids, headings, buttons, your colours, your fonts. Afterwards you drag a column, swap a picture, delete the third card.

Checked on the way in

A block this site does not have never gets stored.

Whatever a tool sends is measured against the blocks that actually exist here. A script tag, a frame, an invented block type — thrown away before anything is written. And what is written is written as a draft where that is possible: a page a tool creates is never published by itself.

Undoable, and written down

Every change from outside is a version.

The same versions your own saves make: open the page in the editor, take the one before, and it is back. Every change also stands in the security log with the name of the key that made it — so you can see which tool did what, and when.

Questions

What is MCP?

The Model Context Protocol: an agreement on how an AI tool talks to a program that is not its own. It has three questions — who are you, what can you do, do this — and tools like Claude, Cursor and Codex all speak it. ambera answers it, so those tools can work on your website without anything being written specially for each of them.

Does this cost me anything per page?

Not here. The tool runs on the person's own side and is billed by whoever provides it. Your website has no AI key for this and calls nobody — it only answers when a tool asks.

Can it break my site?

It can change pages, and every change is a version you take back with one click. It cannot touch users, settings, files or plugins — those tools do not exist. And with a reading key it cannot change anything at all.

Do I have to use it?

No. The switch is off, and while it is off the address answers nothing at all, whatever key is sent. It is there for people who already work with such a tool.

Build with AI Page builder Security All features