Browse the guide›

System

AI access

AI access lets you connect your own AI assistant, for example Claude, to your website. You decide which shops it may change, and it works through the same pages and blocks you edit by hand. Everything it makes opens in the normal page editor, so you can review, change or undo it like any other work.

You find it under System, AI access.

What your AI can do

  • Read your pages and see their blocks and texts.
  • Edit text and images in existing blocks.
  • Add, move, hide and remove blocks. A removed block is kept in the page's trash instead of being deleted for good.
  • Create new pages, or copy an existing page exactly (including its styling). A page made or copied by your AI is always an unpublished draft that belongs to one shop.
  • Change page settings: the title, the address (slug), the search title and description, and "do not index".
  • Translate page titles and search texts into the other languages of a shop. The address in that language is made from the translated title. Text inside blocks is translated by editing the block in that language.
  • Manage the navigation: see what is in the header and footer, and add, change, move, hide and remove entries (or set which pages appear in the menu, on sites that use the simple page-based menu).
  • Upload images (JPEG, PNG, GIF or WebP, up to 10 MB). Images are converted to WebP and stripped of hidden data.
  • Upload videos (MP4 or WebM, up to 50 MB) through tools that can send a file. A chat assistant usually cannot do this; use an image or a link instead.
  • Delete a page. It moves to the trash and goes offline, and you can restore it from the trash. The home page cannot be deleted by your AI.
  • Publish or unpublish pages, but only if you gave it that permission when you created the token.
  • Change the colors and fonts of the whole site (primary, accent, header and footer colors, light or dark mode, heading and body font), but only if you allowed styling changes and publishing. The header and footer text stays readable. Every change reports the previous values, so it can be undone.

Anything visitors would see at once needs the publishing permission. That includes changing a live page, a navigation entry that is already shown, and the site design. Without it, your AI can still prepare everything as drafts: for example a navigation entry for a page that is not published yet appears only when you publish that page.

What your AI cannot do

  • Change styling of blocks (colors, spacing) unless you allowed styling changes when you created the token.
  • Write raw HTML, scripts or embeds, or change where a form sends its messages.
  • Touch anything outside your pages, navigation and design: products, orders, customers, settings and other shops stay out of reach.
  • Change who can log in, or permanently delete pages or blocks. (Removing a navigation entry does delete that entry for good, but it is easy to add again, and your AI can hide an entry instead.)

Text your AI writes is saved in the main language of the shop. Other languages are filled in by translation, and the AI tells you which translations are now out of date.

Shops and shared pages

A token works only for the shops you tick when you create it.

Some pages are shared by all of your shops that use the common content. If your AI edits a shared page, the change appears on every shop that shows it, exactly as when you edit that page yourself. Pages your AI creates are never shared; they belong to one shop.

Create a token

  1. Open System, AI access.
  2. Under New token, give it a name you will recognise, for example "Claude on my laptop".
  3. Tick the shops it may change.
  4. Decide whether it may also publish and unpublish pages. Leave this off if you want to review everything yourself.
  5. Decide whether it may also change styling. Leave this off unless you want your AI to change the colors and fonts of the site.
  6. Choose how long the token stays valid (30 days to 1 year) and select Create token.
  7. Copy the token now. It is shown only once and cannot be shown again. If you lose it, revoke it and create a new one.

Treat a token like a password. Anyone who has it can change the shops you selected until it expires or you revoke it.

Connect your AI

On the AI access page, the server address is shown at the top. It looks like https://your-domain/api/agent/mcp. When you create a token, a window shows ready-to-copy settings for the common assistants.

Assistants that connect by signing in

Some assistants connect to a server by signing in, with no token. For these you only enter the server address. The assistant opens a page on your own site, you sign in if needed, choose the shops and permissions, and select Allow. Use Deny if you did not start the connection yourself.

The connection appears in the list of tokens as the assistant's name with "(sign-in)", and you can revoke it there like any token. The assistant renews its access automatically; a sign-in connection lasts 90 days, after which you approve it again.

Claude Code

Run the command shown in the window. It has the form claude mcp add --transport http my-website <server address> --header "Authorization: Bearer <your token>".

Claude on the web (custom connector)

Open Claude's connector settings, choose Add custom connector, enter a name and the server address, and select Add, then Connect. Claude detects on its own that the server supports signing in (it marks sign in and automatic registration as detected), so you do not need a token. Your site opens its consent page; choose the shops and permissions and select Allow. Claude then lists the available tools. By default Claude asks you to approve each tool before it runs.

If your Claude account offers Request headers in the same dialog, you can instead use a token: add a header named authorization with the value Bearer <your token>. Request headers are a beta feature of Claude and are not available to every organization.

Other assistants

Any assistant that supports remote MCP servers with a fixed request header can use the server address and the header Authorization: Bearer <your token>. Assistants that only offer a sign-in connection use the sign-in method described above.

Working with your AI

  • Ask it to start by looking at your pages and the available blocks, then to build or change one page at a time.
  • New pages are drafts. Open them in Pages, check them in the editor, and publish them yourself.
  • Every change your AI makes is saved as a version of the page, so you can go back to an earlier version from the editor's history.
  • If your AI says a page "changed since it was read", someone else edited the page in the meantime. It will read the page again and repeat its change.
  • A page that is already live can be changed only by a token that may publish. Without that permission your AI will tell you which draft to review.
  • Menu entries that your AI prepares for draft pages appear automatically once you publish those pages.
  • When a site uses the Menu editor, the navigation is changed through the menu tools; on other sites it follows each page's menu settings. Your AI checks which applies.

Revoke a token

In the list of tokens, select Revoke and confirm. The AI that uses the token loses access immediately. The list also shows when each token was last used and when it expires. Expired tokens stop working on their own.

If something does not work

  • "This page is live": the token may not publish. Create a token with that permission, or ask your AI to make its change on a draft.
  • Your assistant cannot connect: check that the server address and the full token were copied, and that the token is still active in the list. For Claude on the web, check that your organization has request headers.
  • Too many uploads: a token can upload a limited number of images per hour. Wait a little and try again.
  • A shop is missing from the list: only the shops of your own account can be ticked.