Can I let Claude or ChatGPT edit my website? What works today
Webflow, Wix, WordPress.com and Framer say yes. Squarespace says no. Every website builder, CMS and host in the library, checked against the vendor's own pages, with what your assistant can actually change.
Margus VeeberYes for more tools than you would guess, and no for one that a lot of small businesses sit on. Checked 24 September 2026: Webflow, Wix, WordPress.com and Framer all let an assistant change a live account. Squarespace does not. Below is every builder, CMS and host in the library with what the assistant can actually do, taken from each vendor's own pages.
One thing before the tables. The question is not whether a tool has an MCP server. Framer has none and is one of the better answers here, because it ships its own agent connection instead. The question that matters is whether your assistant can change something, or only read it. Every row answers that one.
Which website builders can an AI assistant change?
Webflow, Wix, WordPress.com, Framer, Shopify and Lovable all let an assistant make changes to a site or store today. Squarespace does not: its official server only searches domain names. Each one takes a different route in, and the route decides how much setup you face before the first edit.
| Builder | Can it change things? | How it connects | Checked against |
|---|---|---|---|
| Webflow | Yes. Edits CMS items, builds pages and changes styles, with the Designer closed. | Listed connector in Claude, listed app in ChatGPT. Official server. | Webflow's MCP docs, Claude's directory, Webflow's ChatGPT setup page |
| Framer | Yes. Edits the canvas, creates components, creates and deletes CMS items. It cannot touch the published site: every change lands as a branch you review first. | Framer's own agent, for Claude Code, Cursor and Codex. No MCP server, and Framer says so. | framer.com/agents/external |
| Wix | Yes. In Wix's words: manage your account's websites and apps, Stores, Bookings, Blog. Every Wix site also runs a second, visitor-facing server that only reads. | Listed connector in Claude, built by Wix. Official server at mcp.wix.com. | Claude's directory, dev.wix.com |
| WordPress.com | Yes. Drafts posts, updates pages, reads stats and comments, and asks you to confirm every change. Paid WordPress.com plans and Jetpack-connected sites only, not a self-hosted install. | Listed connector in Claude, built by Automattic. | Claude's directory |
| Shopify | Yes, for the store. Creates and updates products, collections, discounts and inventory. The theme and the pages are not in its tool list. | Listed connector in Claude, built by Shopify. | Claude's directory |
| Squarespace | No. The official server generates domain name ideas and checks availability, and its own page says the tools are read-only. Nothing touches a site. | Official server at mcp.squarespace.com, not listed in Claude. Community-built servers exist and are not covered here. | developers.squarespace.com |
| Lovable | Yes. Creates a project, sends it changes, deploys it. | Listed connector in Claude. Official server at mcp.lovable.dev. | Claude's directory |
| Ploy | Not checked. |
Which CMSs can an assistant write to?
Sanity, Storyblok and Contentful each ship an official server that creates, updates and publishes content. Payload needs no server at all, because it lives inside your own codebase and the assistant edits it the way it edits any other code. Of the three hosted ones, Sanity is the only one you add with a click inside Claude.
| CMS | Can it change things? | How it connects | Checked against |
|---|---|---|---|
| Sanity | Yes. Queries and patches documents, prepares a release, and knows your schema without being told. | Listed connector in Claude. Official server at mcp.sanity.io. | Sanity's MCP docs, Claude's directory |
| Storyblok | Yes. Finds, writes, updates and publishes stories, and handles assets. | A config file with a personal token. Not listed in Claude or ChatGPT. Runs on Storyblok's labs host while it settles. | Storyblok's MCP docs |
| Contentful | Yes. Creates, edits and publishes entries, content types and assets. | Add by URL in Claude (mcp.contentful.com), or run it locally with a management token. Not in the connector list. | Contentful's MCP repo, endpoint probed |
| Payload | Yes, without a connector. The CMS is code in your repo, so a coding assistant changes the content model directly. | Claude Code, Cursor or Codex opened on the repo. No first-party server. | Payload's docs |
What about hosting and code?
Vercel, Netlify and GitHub are all listed connectors in Claude, and each one lets the assistant act rather than only report. A site built in code, whether Next.js or Astro, needs no connector at all: the assistant edits the files, GitHub records the change and Vercel or Netlify publishes it.
| Tool | Can it change things? | How it connects | Checked against |
|---|---|---|---|
| Vercel | Yes. Anything your own account can change. Reads deploy logs, project settings, domains and traffic. | Listed connector in Claude plus a Claude Code plugin. ChatGPT by URL, in developer mode on a paid plan. | Vercel's MCP docs, Claude's directory |
| Netlify | Yes. In Netlify's words: create, deploy and manage websites, from secrets to form submissions. | Listed connector in Claude, built by Netlify. | Claude's directory |
| GitHub | Yes. Opens pull requests, reads review threads, checks what a workflow did. A read-only version exists for an assistant that should only report. | Listed connector in Claude. Official server. | GitHub's docs, Claude's directory |
| Next.js or Astro | Yes. It is code. | Any coding assistant opened on the repo. |
What do connector, plugin and add by URL mean?
Three routes in, from least effort to most. A connector is listed inside Claude or ChatGPT by name: search, click, sign in. A plugin is the vendor's own package for Claude Code, and it brings the server with it. Add by URL means pasting the server's address into your assistant's settings and signing in. Below that sits the config file, which is where people who do not write code usually stop.
- Connector: Webflow, Wix, WordPress.com, Shopify, Lovable, Sanity, Vercel, Netlify and GitHub. Nothing to paste.
- Plugin: two lines in Claude Code, server and the vendor's skills included. Vercel and Amplitude ship one.
- Add by URL: Contentful, Optimizely, VWO, Kameleoon. One paste more than a connector, and it works.
- Config file: Storyblok, and every community-built server. Fine if you already live in a terminal.
Does the same list work with ChatGPT?
Less of it, and less of it is verified. Webflow is a listed app in ChatGPT, confirmed on Webflow's own setup page. Vercel, Amplitude, Optimizely and VWO work by URL, which needs developer mode and a paid plan. For every other tool above, the ChatGPT side has not been checked, so nothing is claimed.
The ChatGPT column is thin for a boring reason. Its app directory cannot be probed from outside, so each claim has to come from a vendor's setup page, one tool at a time, and that pass has not been run yet.
What can it change, and what is still off limits?
Content and structure, mostly. The published output is where vendors draw the line. Framer's agent cannot touch the live site and branches every change. WordPress.com asks for confirmation on each edit. Shopify's tools cover products and collections, not the storefront theme. The line moves, and the vendor's own tool list is the record of where it sits today.
- Writes or reads only is the fact that decides a pick. A server that only reports is a dashboard with extra steps.
- Every connection carries your own permissions. If your login can delete a page, so can the assistant. Start with a read task and widen from there.
- Docs lag the product. Optimizely's support page says its server cannot write variation code. It can, and I push variation code through it in production. The tool list beats the doc, and the doc beats a blog.
How was this checked?
Every claim comes from the vendor's documentation or the client's own connector directory, never from a blog or from memory. Each server address was probed on 24 September 2026: a live server behind a login answers 401, a dead one 404. Where a tool's list has not been read, the row says not checked instead of guessing.
Connector directories change weekly, so the date on this page is the date of the claims. The library entry for each tool carries its own check date and the copyable setup block, and the MCP section has the config for every server named here.
Three builders joined the yes column between August and September. Squarespace has an official server with only domain tools on it, which reads like a start rather than a finish, so that row gets rechecked first.
Take something with you
Every entry in the library ends in a block you can copy. Start with the skills.
Browse skills