SEO via MCP in WordPress: live faster, set up safely

With MCP, you let an AI assistant such as Claude talk directly to your WordPress site. That is how we put SEO recommendations live on sites managed by another party, much faster than by hand in WordPress. From WordPress 6.9 it runs through the Abilities API and the MCP Adapter. It becomes safe with limited permissions, approval per change and a log.

This is about clients who give us, as their SEO agency, a monthly programme, while the web build sits with a third party. In our experience their site always runs on a CMS, in about nine out of ten cases WordPress.

This article is for them, and for their web developer. How AI is changing the rest of SEO work is covered in how AI is changing SEO.

Which route fits your WordPress version?

MCP, the Model Context Protocol, is an open standard that lets AI applications connect to external systems ^[1]. How you connect WordPress depends on your version and your platform.

Before 6.9, Automattic's plugin was the usual route. Automattic now points to the MCP Adapter and advises against its own plugin for new installations ^[2]. If a site still runs on an older version, update WordPress first.

From 6.9, the Abilities API is part of WordPress itself: plugins, themes and WordPress use it to describe what they can do, with an input and output schema and a permission check ^[3]. The MCP Adapter, which you install as a plugin or via Composer, turns those abilities into tools for an MCP client ^[4], ^[5]. That is the route we use.

Since 7.1, every ability has a public flag, which is off by default. The MCP Adapter follows that flag, but making something visible is not permission: the user's permissions still apply ^[7].

Two things to know about the adapter. It adds no abilities of its own; those come from WordPress or from plugins ^[4]. And as long as it is at version 0.x, an update can break something, as version 0.6.0 did in August 2026 ^[4].

What does it speed up?

The gain lies in the path from recommendation to live page. In the past, an SEO recommendation went to the web developer as a document or ticket, or someone entered it by hand in the admin area. Now Claude puts the change into the site itself after approval.

Which changes are possible depends on the abilities that are open. Typically these are:

• titles and meta descriptions, often fields of an SEO plugin;
• headings, body copy and FAQ blocks in existing pages;
• internal links and anchor texts;
• alt text for images;
• drafts of new pages or articles, ready for review.

If an ability is missing, for example for the fields of your SEO plugin, someone has to register it first. After that, the pace no longer depends on the web developer's schedule, but on how quickly someone approves.

How do you set it up safely?

Treat the AI like a new employee: its own login, limited permissions and someone looking over its shoulder. An MCP client acts as a logged-in WordPress user and is therefore part of your site's attack surface ^[5]. We recommend these six arrangements:

1. Agree with the web developer. Have them install the adapter and decide together which abilities are opened. For an endpoint reachable over the internet, the WordPress developers mainly recommend read actions: diagnostics, reporting and reading content ^[5]. So every write action is a deliberate choice.
2. A separate user with minimal permissions. Create a dedicated user or role with limited permissions for MCP, certainly in production ^[5]. The Editor role can manage pages and posts, including those of others, but not plugins, themes or settings ^[8]. On a regular site an Editor may post unfiltered HTML (unfiltered_html) ^[8]; if you want it tight, create your own role without that capability.
3. A dedicated application password. You create and revoke it on the user profile, and WordPress shows when and from which IP address it was last used ^[9].
4. Staging first. Test new abilities, adapter updates and large batches on a copy of the site. Actually set that copy up as staging (WP_ENVIRONMENT_TYPE); without that setting, WordPress treats every site as production ^[10].
5. Approval per change. According to the MCP specification, there should always be a human who can refuse a tool call ^[11]. In Claude you approve tool calls; choose "Allow always" only for tools you trust without supervision ^[12], so not for a write action. On top of that, at Izoard no page or article goes live without the client's approval.
6. A log with before and after. WordPress revisions by default only store the title, author, content and excerpt ^[13]. A meta description from an SEO plugin falls outside that by default, so keep track of the old and the new value yourself. The MCP specification recommends logging tool use ^[11], and on the adapter you connect your own logging and monitoring for that ^[4].

One more arrangement: keep tracking outside the MCP permissions. Tags belong in Google Tag Manager, with their own permissions and versions. My colleague Cédric explains how that works in Google Tag Manager explained.

Why does the CMS remain the bottleneck?

MCP is better than manual work in WordPress, but for an SME site the CMS today mainly gets in the way. MCP makes the work faster, not broader: you push everything through the narrow opening that the CMS is. The AI can only do what an ability allows, and an ability can only do what the theme, the page builder and the plugins allow.

Whatever falls outside that remains work for the web developer. Think of a template that gives every service page the same layout, slow code from a page builder or a plugin that writes out its own structured data. The more plugins, the more such limits; why that also matters for security and maintenance is covered in WordPress or a static website.

That is why we build new content sites without a CMS. Then Claude builds the page itself, in HTML and CSS, and that limit disappears. Why and when that fits is covered in website without a CMS.

What should you ask your SEO partner?

Before the start, ask how the connection is set up: which WordPress version and which route, which user, which permissions, which abilities, who approves and where the log is kept. A good answer fits on one page. No answer is a reason to wait.

Want to know first which SEO changes will deliver the most on your site? The free SEO scan looks at technology, indexing, content, internal links and your visibility in AI answers. You get the findings and a conversation, whatever you decide afterwards.