Website Content Updates with MCP: A Step-by-Step Playbook

Website content updates are the small, constant jobs: fixing a price on five pages, refreshing meta descriptions, adding alt text, updating a CMS collection. A marketer or web manager usually does them by hand in the CMS editor, one page at a time. With MCP (Model Context Protocol), an AI app can work with your CMS through its MCP server, so you describe the change once and review what the AI proposes before anything goes live.

This playbook covers the WordPress MCP Adapter, the Webflow MCP server and the Wix MCP server. It is part of our MCP playbooks series. Details were checked against each project's docs on 28 October 2026. eSEOspace did not install or test these servers.

What you need

One MCP client (such as Claude Code, Claude Desktop or Cursor) and the server for your platform.

WordPress. The MCP Adapter README says "WordPress abilities are private by default." A developer sets meta.public to true on each ability they want to expose. The default server then offers three meta-tools: mcp-adapter/discover-abilities, mcp-adapter/get-ability-info and mcp-adapter/execute-ability. The adapter ships no content tools of its own, so what the AI can edit depends on which abilities your site registers. The latest release was v0.7.1 on 16 October 2026.

Webflow. Webflow's MCP overview lists CMS collections and items, pages and SEO metadata, assets, sitemap control and content audits for broken links and missing alt text. CMS items can be published and unpublished. Page branches, for work in isolation, need an Enterprise plan.

Wix. Wix's MCP docs list 18 tools, "all enabled by default." ExecuteWixAPI is "the default way to call site-scoped business-data APIs, such as Bookings, Stores, and CMS." ManageWixSite handles account-level actions "such as creating, updating, or publishing a site."

The workflow

1. Decide what the AI may change. Write a short scope, such as "meta descriptions and alt text on blog posts only." On WordPress, a developer exposes only the abilities that match.
2. Connect with a limited account. On WordPress, run wp mcp-adapter serve with a --user that has an editor-level role, not admin. The CLI guide says that without --user the server "runs as unauthenticated (limited capabilities)." On Webflow, authorize only the workspace you need.
3. Discover what is available. On WordPress, the AI calls mcp-adapter/discover-abilities and mcp-adapter/get-ability-info. On Wix, it starts with WixREADME and ListWixSites, then GetSiteContext. Ask the AI to list what it found before it does anything.
4. Find the content to change. Ask for a list of pages or CMS items that match your scope, such as posts missing a meta description. Webflow's content audit tools can flag missing alt text and broken links.
5. Propose changes in a table. Before writing anything, the AI shows current value, proposed value and URL for each item. A person edits or approves the table.
6. Apply approved changes. On WordPress, the AI uses mcp-adapter/execute-ability with the approved values. On Webflow, it updates CMS items or page SEO fields. On Wix, it uses ExecuteWixAPI or CallWixSiteAPI for CMS data.
7. Publish deliberately. Keep publishing as a separate, approved step. On Webflow Enterprise, page branches let you merge reviewed work into main.
8. Check and log. Spot-check live pages. On Webflow, review the site activity log, which Webflow says records "the changes agents make."

Example prompts

• "Call mcp-adapter/discover-abilities and list every ability you can use on this WordPress site, with what each one does. Don't run any of them yet."
• "List all blog CMS items in Webflow that have no meta description. Propose one for each, under 155 characters, in a table. Wait for my approval."
• "Run a content audit on the Webflow site and list images missing alt text with their page URLs."
• "On my Wix site, use GetSiteContext to confirm the site, then use ExecuteWixAPI to list CMS items in the 'Services' collection where the price field says $99."
• "Apply only rows 1 to 12 from the approved table. Do not publish. Tell me when the drafts are saved."

Guardrails

• Least privilege. Connect WordPress as an editor-level user, not --user=admin. Webflow says agents "work within your existing Webflow permissions and roles." See MCP excessive permissions.
• Expose only what you need. WordPress abilities stay private until a developer marks them public. Review that list whenever you add a plugin.
• Watch the publish tools. Wix's ManageWixSite can publish a site, and every Wix tool is on by default. If your client lets you disable tools, turn off the ones this job doesn't need.
• Treat page content as untrusted. Text on your pages, comments or form entries can carry instructions the AI might follow. Our guide to MCP prompt injection explains the risk.
• Keep custom code human. Webflow's server can add custom code. Keep script and code changes out of AI content work.
• Test upgrades on staging. The WordPress adapter is pre-1.0 and publishes migration guides for v0.3.0, v0.5.0 and v0.7.0.

The MCP security hub covers approvals and logging in more depth.

What to measure

• Time per batch of updates, before and after.
• Share of proposed changes approved without edits.
• Errors that reached the live site, and how they were caught.
• Pages updated per month in the agreed scope.
• For SEO fields, changes in click-through rate in Search Console for updated pages over the following weeks.

Next step

If you run WordPress and want AI edits limited to a few safe abilities, that is custom development work. Our MCP development team can build and review the abilities your site exposes.

Frequently asked questions