What "AI Website Builder" Means Here

"AI website builder" usually means one tool that designs, builds and hosts a site from a prompt. Cmssy is not that. It is a hosted headless CMS: your content and your store live in a Cmssy workspace, and your own app - Next.js, React, Astro or Remix - renders the site on your hosting. Cmssy does not host sites.

What the AI does is run the workspace. An agent works on the content and the store behind your site - pages, translations, SEO, products, discounts, orders and refunds - through the same tools the admin uses. It never touches your code.

Two Ways In: the Assistant and the MCP Server

• The in-admin assistant - press Cmd + K (Ctrl + K on Windows and Linux) in a workspace. It runs with your signed-in permissions, so it can do what your role can do and nothing more. In the page editor it can also generate a page, translate it, or edit the page in front of you on the canvas, where nothing is saved until you save.
• The MCP server - @cmssy/mcp-server connects Claude Code, Claude Desktop or any other MCP client to a workspace with an API token. Same tool core, outside the admin.

Both are on every plan, Hobby included. Cmssy does not ship a model: you bring a key from Anthropic, OpenAI, Google, Mistral or Groq, and the provider bills you directly.

MCP on its own is not rare any more - Contentful, Sanity, Storyblok and Payload ship MCP servers too. What matters is what the tools let an agent do, and what stops it.

Content Work

• Create pages and add, edit, reorder or remove blocks, using the block types your site registers.
• Write and rewrite copy, and translate pages into the languages the workspace has enabled.
• Generate a page's meta title and description, and derive brand tone and keywords from your published pages.
• Manage models and records, media, forms and form submissions.
• In the assistant, export anything it can read as CSV, JSON or Markdown.

Store Operations

On a plan with cart and checkout (Pro and up), the same agent works the back office:

• Orders - list and read orders, create one by hand, edit its lines, record a full or partial payment, attach an invoice, move it through fulfillment and along your order pipeline, or cancel it.
• Refunds - full or partial, with a reference for your records.
• Discounts - percentage, fixed-amount or free-shipping codes with start and end dates, a minimum subtotal and a usage cap; switch them on or off.
• Products - bulk updates and price tiers.
• Customers - look up an account, suspend or reinstate it, send a password reset.

Cmssy records payments; it does not move money. A refund the agent records is the record in Cmssy - your payment provider still sends the money back, through your integration.

Confirmation Before Anything Destructive

Reads run immediately. The tools whose effect is hardest to undo - refunds, order cancellations, page deletes and publishes, bulk product updates and deletes, customer suspension among them - do not act on the first call. They return needsConfirmation: true, a one-line summary of what would happen and a reference, and nothing changes. Once you approve, the agent repeats the call with that reference.

A reference works once, expires, and only with the exact arguments it was issued for - change the amount of a refund and the server asks again. In the admin assistant you approve with a button in the chat, and any other write is described first and runs only after you agree. Over MCP, the agent shows you the summary before it confirms.

What It Does Not Do

• It does not write your code. No tool writes a file, edits a component or opens a pull request; block schemas stay in your repository, under review.
• It does not host or deploy anything. Your app does that, on your hosting.
• It does not move money. Payments and refunds go through your provider; Cmssy records them.
• It does not manage your team. The assistant can list members and roles but cannot invite, remove or reassign anyone.
• It cannot exceed your role. The tool set is built from your permissions at the start of every run.

What to Look For in an AI-Enabled CMS

• Verbs, not only CRUD - can the agent refund, fulfil and discount, or only create and update records?
• A confirm step on the irreversible - enforced by the server, not left to the prompt.
• Your own key - which model, whose bill, and which plan it needs.
• Permissions - does the agent act as you, with your role, or with a master key?
• Code stays yours - a content change should never need a deploy, and an agent should never need write access to your repository.

Getting Started

1. Add a provider key - Settings → AI Provider in the admin, then press Cmd + K. See the assistant docs.
2. Or connect an MCP client - create an API token and add @cmssy/mcp-server to your client's config. See the MCP server docs.
3. Render it in your app - start from cmssy-io/examples, or wire your own app with the installation guide. To see the store side running, open the demos.