# Squarespace or Wix: Which Is Better for Editing With AI?

Canonical: https://figment.so/blog/squarespace-vs-wix-for-ai-editing

Both have real in-editor AI: Squarespace in one Clarkson chat, Wix across Aria and several generators. For an outside AI agent, Wix's developer MCP does far more. Squarespace's official MCP covers domain search only.

**Both platforms have real AI editing inside their own editors: Squarespace puts it in one Clarkson chat, and Wix spreads it across Aria and several generators. For an outside AI agent using an official, documented connection, Wix goes much further, because Wix publishes a developer MCP server that acts on live sites and Squarespace's official MCP is limited to domain search.** Neither platform lets an outside tool rewrite your page layout directly through an API. That stays in each platform's own editor, reachable by hand or through a signed-in browser agent.

## What does each platform's own AI do on an existing site?

**Squarespace's Clarkson AI chat** works inside the page editor and, per Squarespace's help center, can "add or replace images in image blocks," "change text on a page or in blocks," "create and edit products and discounts," "draft and schedule email campaigns," "edit and manage contacts," "review and summarize your site's analytics," and "update your site styles" ([Squarespace, "Using Squarespace AI"](https://support.squarespace.com/hc/en-us/articles/16282290976013-Using-Squarespace-AI)). It is a real edit surface on a page you already have, but not everywhere yet: "We're rolling out Clarkson to sites in waves, so it may not be available on your site yet" (same source). Blueprint AI Builder separately generates a new starting site from a description. It does not edit an existing one.

**Wix's built-in AI** is split across several named tools rather than one chat: an AI Website Builder that generates or regenerates a whole site from a conversational brief, Aria as the in-editor assistant for generating or editing text, an AI section generator, an AI image and logo generator, AI product descriptions, AI marketing emails, and an AI tool for creating CMS collections ([Wix, "AI Tools: An Overview"](https://support.wix.com/en/article/about-wixs-ai-tools)). Like Clarkson, all of it runs inside Wix's own editor and dashboard, so a person (or an agent driving the browser) still does the work.

## What can an outside AI agent do through each platform's API or MCP?

Wix allows much more. Squarespace's official MCP server does one job, domain search. Its developer preview docs list two tools, one that generates brandable name and domain ideas and one that checks real-time domain availability and pricing, and state that "No tool registers a domain or charges a payment method" ([Squarespace Developer Platform, "Overview of the Squarespace MCP Server"](https://developers-preview.squarespace.com/mcp/overview)). Squarespace's REST APIs split into two kinds. The **Products API** can "create product" and "update product," which is real write access to store items ([Squarespace Developer Platform, Products API](https://developers.squarespace.com/commerce-apis/products-overview)). The **Website API** "provides read-only access to several core resource objects" such as site metadata and store-page listings, not page layout or design ([Squarespace Developer Platform, Website API overview](https://developers.squarespace.com/commerce-apis/website-overview)). Nothing documented lets an outside agent change a page's content or styles except by driving the editor itself.

**Wix publishes a broader developer MCP.** "The Wix MCP is a Model Context Protocol server that lets you work with Wix from your AI agent. Once you connect it, your agent can search the Wix documentation, write code for the Wix platform, and make API calls on Wix sites," and it is "also available as a built-in connector in Claude" ([Wix Developers, "The Wix MCP"](https://dev.wix.com/docs/overview/ai-the-wix-platform/the-wix-mcp), last updated 30 August 2026). Its documented capabilities go beyond read access: "Call APIs on sites: Your agent can perform real actions on a site, like applying a discount to all store products, adding a bookings staff member, or sending an email to a contact," and "Manage sites, apps, and projects: Your agent can perform account-level actions, like creating and publishing a site, installing a business solution, or scaffolding a new headless project" (same source). By default the agent "authenticates through your Wix account," so it acts with your own permissions. Use it from an account whose role fits the task. It covers business data, CMS collections and site and app management. It is not an API for repainting an existing page's visual layout, which Wix keeps inside its own Editor.

Every Wix site also runs a separate, automatic **Wix Site MCP** at `<your-site.com>/_api/mcp`, but that one is for visitors, not owners: "The MCP only uses public information that's already available on the business's site," for questions, bookings and purchases, "with no additional setup required" ([Wix, "AI Tools: Connecting Wix Sites to AI Platforms"](https://support.wix.com/en/article/ai-tools-connecting-wix-sites-to-ai-platforms)). An owner's own agent cannot use it to edit anything.

| | Squarespace | Wix |
| --- | --- | --- |
| Built-in AI edits an existing page | Yes: Clarkson AI chat (text, images, products, styles), rolling out in waves | Yes: Aria and section/image/text generators, inside the Editor |
| Official MCP server | Yes, but domain-search only, read-only, preview status | Yes: a broader developer MCP with business-data actions, CMS, site creation/publishing |
| Documented write API beyond commerce data | Products API only (store items) | Site APIs across business solutions, e.g. store discounts, bookings staff, contact emails (examples from Wix's MCP docs) |
| Outside AI editing page layout/design directly | Not documented on any route | Not documented on any route |
| Browser-agent route (ChatGPT Work, Claude) | Possible, signed-in, task-by-task | Possible, signed-in, task-by-task |
| Role for a limited human or agent account | Website Editor: "can add products, blocks, and other content to existing pages... can't add new pages or make style changes" ([Squarespace](https://support.squarespace.com/hc/en-us/articles/206537297-Contributor-roles-and-permissions)) | Custom roles built from Roles & Permissions, scoped to only the content-edit rights a task needs ([Wix](https://support.wix.com/en/article/roles-permissions-overview)) |
| Export if you leave | No HTML/CSS export; one blog+layout page exports to XML; commerce orders to CSV | No HTML/CSS export ("your site must run on Wix's servers"); CMS collections export to CSV, one at a time |

## Which should I choose?

Choose Wix if you want an outside AI agent to take real actions through an official, documented connection, because its developer MCP can apply store discounts, add a bookings staff member or send an email to a contact. Choose Squarespace if you want one chat inside the editor that changes text, images, products and styles on a page you already have, and check that Clarkson has reached your site, since it is rolling out in waves. Choose either if you only need a signed-in browser agent to work task by task. For redesigning an existing page's layout through an API with no browser, neither platform documents a route.

## Which role should I use for a limited account?

On Squarespace, use the **Website Editor** permission. It is the closest fit for handing an agent (or a junior collaborator) day-to-day content work: it can add blocks and products to pages that already exist but "can't add new pages or make style changes." Wix does not name a single equivalent role. Instead it lets you build a **custom role** with only the content permissions a task needs, rather than choosing between a fixed "everything" or "almost nothing" role. Either approach beats handing an agent your owner login. For the platform-by-platform version of this question, see [how to give an AI agent access to your website without handing over your login](/blog/give-ai-agent-access-to-your-website).

## Can an outside agent redesign an existing page through an API?

No, on neither platform. If you want an outside coding agent such as Claude, Cursor or Codex to rewrite an existing page's visual layout through an API with no browser involved, neither platform documents that today. Squarespace's MCP does not touch site content at all yet. Wix's MCP reaches business data, CMS collections and site creation and publishing, which is real and useful, but it is not layout editing of an existing page. That is still an Editor job, either by hand or through a signed-in browser agent.
