How to Manage Your WordPress Site from a Chat with AI Agents (MCP)
You can now connect Claude or ChatGPT to your WordPress site and ask it to audit SEO, draft posts or fill in alt text. Here is how the setup works, what to expect and how to keep it safe.
A year ago, “AI and WordPress” mostly meant a button in the editor that wrote a paragraph for you. Today you can open a chat with Claude, ChatGPT or Gemini, point it at your website, and say: “list the 20 most recent posts with no meta description and suggest one for each.”
That is a big change for affiliate websites. Most affiliates run content-heavy WordPress sites with hundreds of reviews, bonus pages and comparison tables. A lot of the maintenance work is repetitive: adding or updating content, fixing titles, updating outdated bonuses, adding FAQs. It is exactly the kind of work an assistant can do well, as long as you set it up carefully.
This guide explains what is possible, how to set it up, what an AI agent can and cannot do on your website, and how to keep your live site safe while you try it.
Two Different Things Called “AI in WordPress”
The first source of confusion is that two quite different things can get the same label.
1. AI features inside the WordPress admin. The official WordPress “AI” plugin (on wordpress.org, still experimental at the time of writing) adds AI helpers inside the dashboard and the block editor: suggested titles, excerpts, alt text, meta descriptions, translation, comment moderation and editorial notes. You bring your own provider key and connect it through a connector plugin (Settings → Connectors). It is useful, but you are still the one sitting in wp-admin clicking buttons. It does not let a chat app manage your site.
2. A chat agent that operates your website. Here you stay in Claude or ChatGPT and talk to it. The agent connects to your website through a standard called MCP, and it can read and change content on your behalf, within the permissions you give it.
This article is about the second one. The two are not mutually exclusive, but they solve different problems, and installing the first will not give you the second.
How It Works
MCP stands for Model Context Protocol. Think of it as a standard plug that lets an AI app talk to another system. Instead of every AI company building a separate integration for every platform, there is one common way to connect them.
On the WordPress side, two pieces make this work:
- The Abilities API. Since WordPress 6.9, core has a way for plugins and themes to register “abilities”. An ability is a single action, like “create a post” or “update the post title”, with a defined set of inputs and a permission check. Abilities are private by default; they only become available to outside tools when marked public.
- The MCP Adapter. This is the official plugin that takes those abilities and exposes them as tools an AI app can use. It also provides a small set of general tools so the agent can discover what is available on your site and run it.
So the chain is: your chat app → MCP → the adapter plugin → the abilities on your site → WordPress, always checked against the permissions of a real WordPress user.
The result: the agent can only do what your website has explicitly exposed, and only what the logged-in user is allowed to do.
Which Setup Is Right for You?
It depends on where your site lives and which chat app you want to use.
If you work with coding agents like Claude Code or OpenAI Codex, you may not need any of this: they run in your terminal and can talk to WordPress directly through its REST API or WP-CLI.
MCP is what you need when you want to manage the site from a regular chat app, such as Claude, ChatGPT or Gemini. That takes a couple of plugins.
How to Connect WordPress to Claude, ChatGPT or Gemini
You will need WordPress 6.9 or newer and PHP 8.0 or newer (required by Enable Abilities for MCP). Do this on a staging website first (more on that in the safety section).
Step 1: Install the plugins
Install two plugins from the WordPress plugin directory:
- MCP Adapter (the official one) - download here.
- Enable Abilities for MCP (by Fabio Montenegro) - download here. It requires the MCP Adapter, and it adds a settings screen for choosing what the agent may do, plus the sign-in that your AI agent’s custom connectors need.
Activate both.
Step 2: Choose which abilities to enable
Go to Settings → WP Abilities → Abilities tab. You will see a long list of abilities grouped by category. At the time of writing the plugin offers over a hundred, across about twenty categories: posts, pages and custom post types, categories and tags, media, comments, menus, SEO fields, WooCommerce and other integrations, search and replace, and site stats.
Enable only what you need for the job at hand. Destructive abilities (deleting content, for example) are off by default; leave them that way.
Step 3: Enable OAuth sign-in
Open the Connection tab and enable the OAuth connector. This is what lets Claude, ChatGPT or other agents sign in to your website the way you sign in to any app with “Log in with…”, instead of you pasting passwords around.
Step 4: Add the connector in your chat app
The idea is the same everywhere: add a custom connector, paste your site URL, then sign in to WordPress and approve a consent screen. Menu names change often, so treat these paths as a guide.
- Claude: in claude.ai, go to Settings → Connectors → Add custom connector and paste your site URL. Claude sends you to your WordPress login page to sign in and approve.
- ChatGPT: turn on Developer Mode under Settings → Apps & Connectors → Advanced settings, then create a new connector with your site URL and OAuth as the authentication method. Once connected, switch the connector on from the tools menu in the chat. At the time of writing this requires a paid plan.
- Gemini: on gemini.google.com, go to Settings → Connected Apps → Add a custom app, paste your site URL and approve in the browser. At the time of writing this is rolling out to personal accounts in the US only; Gemini Enterprise teams add MCP servers from the admin’s Connected apps settings instead.
I tested this setup with Claude. Any app that supports remote MCP servers with OAuth sign-in should work the same way.
A few things worth knowing:
- Each person connects with their own WordPress account, so the agent acts with that user’s role and permissions.
- All actions the agents take are logged per user, so you can see afterwards what was done and by whom.
- Your website must be reachable from the public internet over HTTPS. A local install, a website behind authentication or a firewalled staging site will not work.
That is the whole setup. Open a new chat, make sure the connector is enabled for it, and ask something simple like “what are the 5 latest posts on my website?”
Other options
The plugin above is not the only way. Others exist, such as Royal MCP, Easy MCP AI (from Themeisle), miniOrange Secure MCP Server, WPVibe and AI Engine. They differ in what they expose and how they handle sign-in. I have not compared them here; pick what fits your setup, and apply the same cautions.
What to Expect: What an Agent Can and Can’t Do
After the first connection, I asked Claude connected to a live website to describe its own abilities and limits. Its answer matches what I saw in practice, and it’s worth knowing before you plan your work.
What it can do
- Content: posts, pages, custom post type items, categories, tags, media and comments.
- On-page SEO fields across Rank Math, Yoast and SEOPress, including schema.
- Menus.
- Translations, if a multilingual plugin is active.
- Cache purging.
- Read-only audits: missing alt text,
llms.txt, sitemap, plugin list, environment details.
What it can’t do
- Install, update or activate plugins and themes.
- Change WordPress or plugin settings (permalinks, for example).
- Edit theme or plugin files, CSS or templates.
- Visually edit page-builder layouts. It works with the underlying HTML and cannot see how the page renders.
- Create, edit or delete users.
- Touch the database, server, DNS or hosting.
- Activate PHP snippets. An admin has to approve those.
In other words, it is a capable content and SEO assistant, not a sysadmin and not a designer. If a task involves how the site looks or how the server is configured, you still do that yourself.
One more note from the same conversation: it recommended working drafts-first and showing proposed bulk changes before applying them. That is good advice, and I built it into the prompts below.
What It’s Good For on an Affiliate Website
These are the jobs where I think the time saving is real:
- Bulk SEO audits. Find titles that are too long or duplicated, missing meta descriptions, missing focus keywords.
- FAQ schema. Add structured FAQ data to review and comparison pages.
- Alt text. Fill in missing image descriptions across the media library.
- Updating outdated content. Find posts that mention last year’s bonus, an expired offer or an old date, and propose edits.
- Internal links. Suggest relevant links between related reviews and guides.
- Comments. Sort spam and genuine questions, and draft replies.
- Drafting posts. Create first drafts, saved as drafts, for you to edit.
Example prompts you can paste
Start with read-only requests, then move to changes once you trust the results.
-
Meta description audit: “List my 20 most recent posts that are missing a meta description. For each, propose one under 155 characters. Don’t save anything yet.”
-
Alt text: “Find images in the media library with no alt text that are used in published posts. Show me 15 of them with suggested alt text, and wait for my approval before updating.”
-
Outdated bonus mentions: “Search my published posts for the text ‘2025’. List the posts and the exact sentences where it appears, and suggest updated wording. Don’t edit anything.”
-
FAQ schema: “Take the review post at [URL]. Draft five questions and answers based only on the content already on the page, add them as FAQ schema in the SEO plugin, and show me the result before saving.”
Notice the pattern: ask for a list, ask for a proposal, say “don’t save yet”. You stay in control, and you catch mistakes before they reach your live pages.
Once you’re comfortable with the results, you can start using prompts that update your content. For a test I asked Claude to add a Spacer block:
can you edit the homepage and add a 20px spacer before the separator block at the end of the page?
It did, and responded:
Done. I added a 20px spacer block to the homepage (page ID 18), directly before the separator that sits above the Responsible Gambling note at the bottom. Exactly one replacement was made, so nothing else on the page was touched.
Safety
Both plugins are new and still evolving, and you are giving software the ability to edit your website. A little caution wouldn’t hurt.
- Test on staging first. The same logic as for any update: see my post on testing WordPress updates safely. Take a backup before the first real run.
- Use a dedicated WordPress user for the AI, with the Editor role rather than Administrator. That limits the damage if something goes wrong.
- Enable only the abilities you need. You can always turn more on later.
- Keep destructive abilities off. Deleting content is rarely something you want to delegate.
- Work in drafts, and ask for a preview. Have the agent create drafts and show the proposed changes (before and after) before any bulk update.
- Review the activity log from time to time to see what was actually done.
- Revoke access when you’re done. Remove the connector in Claude, ChatGPT or Gemini and, if you no longer need it, disconnect it or deactivate the plugin in WordPress.
- Check the basics: a public HTTPS address, and a chat-app plan that supports custom connectors (not every free plan does).
Wrap-Up
Letting an AI agent work on your WordPress site is no longer an experiment for developers only. With WordPress 6.9, the MCP Adapter and a plugin that handles sign-in, a non-technical site owner can have Claude, ChatGPT or Gemini audit SEO fields, draft content and clean up media from a chat window.
It will not replace your judgment and it is not magic: it works through a defined list of actions, with the permissions of the account you give it. Start small, work on staging, keep a human in the approval loop, and expand as you build trust.