Web
Can an AI agent run your website? WordPress, Wix, Shopify, and Webflow compared
All four major website platforms now let AI assistants connect through the Model Context Protocol. That does not mean an agent can run your site. The real differences are in how much of the site it can reach, whether you can review a change before it goes live, and what record it leaves behind.
The short answer
Not yet, on most platforms—but an assistant can already take over specific jobs. WordPress offers the most mature content access through WordPress.com and Jetpack-connected sites. Wix lets agents take real actions through its APIs. Webflow covers design, pages, and existing CMS items. Shopify’s official servers focus on shopping and developer tools, so editing the store admin usually depends on third-party connectors. Before choosing, check five things: reach, preview, permissions, recovery, and records.
What “running a website” actually involves
After launch, most of the work on a site is not design. It is publishing and updating articles, keeping products and prices current, translating content, fixing SEO issues, handling form submissions, and making routine edits to menus, banners, and pages. An assistant is useful to the degree it can reach that work safely. That gives five practical questions for any platform:
- Reach: which parts of the site can the assistant read and change?
- Preview: can you see the effect of a change before it is saved or published?
- Permissions: can access be limited to specific areas or actions?
- Recovery: do changes land as drafts or versions you can restore?
- Records: is every change logged with who—or what—made it?
WordPress
WordPress has two separate routes. The WordPress.com MCP server works on all WordPress.com paid plans and on self-hosted sites connected through Jetpack with a Jetpack AI or Jetpack Complete plan. Since March 2026 it includes write operations: 19 operations across posts, pages, comments, categories, tags, and media. New posts default to drafts, deleted items stay in the trash for 30 days, actions are recorded in the Activity Log, and access can be set to read-only or switched on tool by tool.
Other self-hosted sites can use the official MCP Adapter plugin, built on the Abilities API that arrived in WordPress 6.9. Out of the box it exposes little beyond site information; content abilities have to be added by plugins, and a recent review notes that the adapter itself provides no dry run or staging. In practice, what an agent can do on a self-hosted WordPress site depends on which plugins you install and how well they handle permissions.
Wix
The Wix MCP lets an agent perform real actions on a site through Wix APIs—Wix’s own examples include applying a discount to all store products, adding a bookings staff member, and sending an email to a contact—as well as creating and publishing sites. The agent signs in with your Wix account, or with an API key for automation tools. The documentation does not describe permission scoping, previews, or an action log, so check these with Wix before giving an agent access to a live business site.
Shopify
Shopify has invested heavily in agents, but mostly on the shopping side. According to a developer guide to Shopify’s MCP servers, its official servers cover storefront shopping (products, carts, and policies for shopping agents), customer accounts, and developer documentation. They do not let an outside assistant manage the store admin. Merchants who want that use third-party servers built on the Admin API, which Shopify does not vet, with access controlled by the token’s scopes. Inside the admin, Shopify’s own assistant, Sidekick, works only within Shopify.
Webflow
Webflow’s official MCP server reaches further into design than the others: agents can work with elements, styles, components, variables, pages, assets, and existing CMS items, though not create new localized CMS items. Agents act within your existing Webflow roles, and each authorization covers one workspace. For isolation, page branches let an agent work on changes separately and merge them later, but branches require an Enterprise plan.
Side by side
| Reach | Preview before saving | Permissions | Recovery | Record of actions | |
|---|---|---|---|---|---|
| WebX (our platform) | Every section of the admin panel | Dry run for every change | Read or write per section, per agent key | Drafts and versions with restore | History of every change |
| WordPress.com and Jetpack sites | Posts, pages, comments, categories, tags, media | The assistant asks for approval before each request | Read-only or per-tool switches, plus user roles | Drafts by default; 30-day trash | Activity Log |
| Self-hosted WordPress (MCP Adapter) | Only what installed plugins expose | Not provided by the adapter | Permission checks written by plugin developers | Depends on the plugins | Requires a logging plugin |
| Wix | Actions through Wix APIs; creating and publishing sites | Not described in the documentation | Not described in the documentation | Not described in the documentation | Not described in the documentation |
| Shopify | Official: shopping and developer docs. Admin: third-party servers | Depends on the third-party server | Admin API token scopes | Depends on the third-party server | Depends on the third-party server |
| Webflow | Design, pages, assets, existing CMS items | Page branches on Enterprise plans | Existing Webflow roles, one workspace | Page branches on Enterprise plans | Not described in the documentation |
How to choose
- You run a content site on WordPress.com or can use Jetpack: the built-in MCP server is the most complete ready-made option for articles and pages.
- You run self-hosted WordPress without Jetpack: treat AI access as a plugin project, and review each plugin’s permissions before enabling write access.
- You are on Wix: start with read-only and low-risk tasks until you have confirmed how permissions and logging work for your plan.
- You run a Shopify store: expect official agent support to help customers shop, and evaluate any admin connector as you would any third-party app with access to your store.
- Your site is design-led on Webflow: agents are strongest at structured edits; plan for Enterprise if you need isolated changes.
- You are planning a new site where content is a bottleneck: choose a platform where agent access covers the whole site and every change is reviewable.
Whichever platform you use, start an assistant with drafts and limited access, and widen its permissions only when the results justify it. We explain that approach in AI agents for business: choose the job before the platform, and the basics of the protocol in what an MCP server means for your website.
See how sites we build on WebX handle AI access, or read about our web development process.
FAQ
Questions teams ask.
Can ChatGPT or Claude update my WordPress site?
Yes, if your site has an MCP server they can connect to. WordPress.com sites on paid plans and self-hosted sites with Jetpack AI or Jetpack Complete can use the WordPress.com MCP server. Other self-hosted sites need the MCP Adapter plugin plus plugins that expose the actions you want.
Does Shopify let AI agents manage my store?
Shopify’s official MCP servers are aimed at shopping agents, customer accounts, and developers. Managing the store admin through an outside assistant typically requires a third-party server built on the Admin API. Shopify’s built-in assistant, Sidekick, works inside the admin.
Which platform is safest for AI agents?
Look for limited permissions, a preview or approval step, drafts or versions you can restore, and a log of every change. Platforms differ most on these points, and some do not document them at all.
Should I switch platforms to use AI agents?
Rarely for AI alone. Start with what your current platform supports. Switching makes sense when you are rebuilding anyway, or when content work is a real bottleneck and your platform cannot give an assistant safe access to it.