Automate WordPress with MCP: 10 Tasks We Actually Tested

Most people think you can only automate WordPress with MCP for one task: publishing blog posts. That’s the smallest part of it.

Once your site is connected, you can automate WordPress with MCP for actual work, not just posts. Managing users, checking plugins, and cleaning up comments. Running a full alt text audit across your whole media library. All from a plain-language prompt without any dashboard clicking.

We tested all ten of these on a real site, with the exact prompts we’re sharing below. Here’s what worked, what needs a review step, and how to try each one yourself.

Quick Answer

You can automate WordPress with MCP for far more than publishing blog posts. Once your site is connected with an AI client, an AI agent can manage users, check plugin updates, moderate comments, fix SEO metadata, edit menus, add code snippets, and audit your media library for missing alt text, all from plain-language prompts. Read-only tasks run immediately, while anything that changes your site, like updating a plugin or publishing content, pauses for your approval first.

1. Draft and Publish Blog Posts From a Prompt

The most common way to automate WordPress with MCP is drafting and publishing posts. You describe a post, the agent writes it and saves it, either as a draft or published live, using the WordPress REST API.

Prompt to try:

Write a 1,000-word post about choosing a WordPress host and save it as a draft.

What happened: The agent wrote a full ~1,020-word draft, titled it “How to Choose a WordPress Host (Without Wasting Money on the Wrong One),” and saved it straight to the WordPress editor as a draft. Nothing went live. The content covered real ground, shared vs. VPS vs. managed hosting, renewal pricing traps, what to check before you commit, in plain editor blocks, not locked into a page builder.

The key detail is the “save as a draft” part. The post becomes ready to review as prompt, so a human still approves before anything goes live. To set this up, you connect your site through the WP Vibe MCP plugin, which turns it into the server the agent writes to.

2. Bulk Content Edits Without a Full Rewrite

This is one of the most useful ways to automate WordPress with MCP, targeting edits across many pages at once. A phone number, a CTA, an old brand name. Normally that means opening each page one by one.

With MCP, the agent does a targeted find-and-replace instead. It patches just the matching text directly, without reading and rewriting the whole page, which is faster and far less risky than regenerating full content.

Prompt to try:

Find the last month's posts that contain the text "Book a Free 30-min Call" and replace it with "Schedule a demo." Show me a list.

What happened: The agent searched the last month’s posts and found one match. But it caught something first. The actual text on the page read “Book a free 30-minute call,” worded slightly differently from what was typed. Instead of forcing a replacement or ignoring it, the agent flagged the difference and asked for confirmation.

Once approved, it made the swap. The visible CTA changed to “Schedule a demo,” while the link behind it stayed exactly the same. On the live page, the call-to-action now reads “Schedule a demo and we will audit your current system,” with only the wording updated and nothing else touched.

It also confirmed that was the only post with that phrase, so nothing else needed editing.

The important part is that it “asks before acting on a near-match.” A blind find-and-replace would either miss the match or change the wrong thing.

3. User and Role Management

Knowing who has access to your site matters, especially when old contractors, agencies, or team members still have accounts they no longer need.

MCP handles this cleanly. You can list users, check roles, create accounts, or remove access, with a confirmation step on anything that changes permissions.

Prompt to try:

List every user on this site with Administrator or Editor access, and don't change anything, just show me the list.

What happened: The agent pulled a clean table with the username, display name, email, role, and registration date for each account, then summarized it in one line: three administrators, zero editors.

It also flagged something it wasn’t asked for. One author-level account existed on the site but didn’t meet the administrator or editor filter, so it was left out of the main list and mentioned separately.

Reading the list is step one. From there, removing access is a simple follow-up like “remove Editor access for [email],” which triggers a confirmation before it runs, since anything that changes permissions is treated as sensitive. Clearing out old accounts is a big part of managing WordPress user access, and MCP makes the check a one-line job. 

4. Plugin and Theme Update Checks

Outdated plugins are the reason why WordPress sites get compromised. Checking them manually across a big site is time-consuming, which is exactly why it gets ignored.

You can automate WordPress with MCP to check every plugin in one prompt. The agent lists everything installed, flags what’s active or inactive, and reports update status, so you can see the whole picture at a glance.

Prompt to try:

List every plugin installed on this site, and show me which ones have updates available, and flag anything that hasn't been updated in over a year. Don't update anything yet, just show me the list.

What happened: The agent returned a full table of all 24 installed plugins, name, version, and active or inactive status for each, with a clear summary at the end.

One limit showed up here. The agent said it couldn’t fully check for available updates because of network access limits. So it confirmed what’s installed and running, but checking each plugin against its newest version needed a different permission or a second step.

It’s a good reminder: this only works if the server can access outside sources, like the WordPress plugin repository and not just your own site.

After you look over the list, updating a plugin is a confirmed step. The agent shows what’s changing and waits for your okay before it touches anything. It handles the check, but the actual updating and testing is still on you, which is where ongoing WordPress maintenance helps for sites that can’t fall behind.

5. SEO Metadata at Scale

You can automate WordPress with MCP to fix metadata across many posts at once. Meta titles and descriptions are the most important factor of SEO, and mostly people ignored them, not because they are hard but because fixing them one by one takes time.

MCP integration with WordPress is a very good fit for this since most sites run Rank Math or Yoast. The agent can read and update meta fields across many posts at once.

Prompt to try:

List the posts with outdated meta descriptions. Don't change anything, just show me which ones need it.

What happened: The agent didn’t just look for blank fields. It read the actual descriptions and identified a subtler problem.

Out of 16 posts with meta descriptions, it flagged several as outdated. Some referenced “2025” as if it were still current. Others were simply nine-plus months old with no updates.

That’s harder to catch by hand. A blank field is obvious. A filled-in description that’s quietly gone stale is easy to scroll right past.

From there, rewriting them is a quick follow-up, and asking to see the new text before it saves keeps you in control. This kind of cleanup is a core part of improving WordPress SEO without clicking through every post by hand.

6. Nav Menu Management

Menus can be difficult to edit manually. You have to add a page, move it into place, set the order, and check that everything is in the right place. It’s easy to make a mistake.

MCP builds and updates menus through the WordPress REST API. It reads the current structure, then makes the change you ask for.

Prompt to try:

Add a new item called "States" to the Primary menu, linking to /states, and place it right after "Services." Show me the change. 

What happened: The agent pulled the current menu first. It found something worth catching. A “States” item already existed as a dropdown.

Instead of making a second, confusing “States” link at the top level, it placed the new page under the existing dropdown. The live result is one clean “States” menu item, not two identical labels sitting side by side.

That’s the pattern again. It followed the instruction but caught a naming clash before it made a mess.

This all runs on the menu endpoints built into WordPress’s REST API for menu items, which is what lets an agent read and edit navigation without a plugin.

7. Comment Moderation

Busy blogs get flooded with comments. Sorting real ones from spam by hand eats time you don’t have.

MCP handles the whole loop. It can list pending comments, approve the real ones, flag spam, or reply, all through the REST API.

Prompt to try:

Show me all comments waiting for approval on this site. Just the list, don't do anything else.

What happened: The agent returned eight pending comments in a table, ID, author, which post each one landed on, and the date.

A few of the usernames gave the game away right off. Handles like “linkvofull88” and “mxplinko777” are classic spam signatures, random letters and numbers, with no real name.

That’s the point of pulling the list first. Some spam shows itself in the account name alone, before you read a single comment. You can triage the obvious ones fast, then look closer at the rest.

From there, cleanup is simple. Tell it to mark the spam ones, approve the real ones, and leave anything borderline for you to check. Just keep the “show me the list first” habit so nothing gets flagged wrong.

8. Site Health and Performance Audits

A slow site loses visitors and rankings. But “your site is slow” doesn’t help unless you know what’s actually causing it.

You can automate WordPress with MCP to run a full site audit. It scores performance, accessibility, SEO, and best practices, then lists the real issues, not just a number.

Prompt to try:

Run a site health check on the homepage. Give me the performance, accessibility, and SEO scores, plus the top 3 issues actually worth fixing. Don't fix anything yet, just show me the report.

What happened: The report came back with real scores. Performance 60, Accessibility 85, SEO 100, Best Practices 96.

It also showed the Core Web Vitals behind the performance score. The biggest problem was a Largest Contentful Paint of 10.7 seconds, way over the 2.5-second target that Google recommends in its Core Web Vitals documentation.

Then it ranked the top three fixes.

First, unused CSS, about 245 KiB to trim, likely from page builder bloat. Second, unused JavaScript, 103 KiB of scripts loading but never running, with a fix suggested: remove or lazy-load them. Third, a color contrast issue affecting low-vision users, with the exact fix named.

That’s the difference. Not “performance needs work,” but what’s wrong, how bad it is, and what to do about it.

9. Custom Code Snippets

Adding a tracking script or a small function usually means editing theme files or installing yet another plugin. Both are easy to get wrong.

MCP handles it through a snippet manager instead. It can add a tracking code, a small PHP function, or a CSS tweak without touching your theme files directly.

Prompt to try:

Add a Google Analytics tracking snippet to the site header using WPCode. Show me the exact code before you activate it.

What happened: Before writing anything, the agent stopped and asked. It showed an “Approval required” prompt, named the exact action, and warned plainly that this would run a code change on the live site.

Only after that did it show the code for review. Once approved, it saved the snippet, named it “Google Analytics,” set it to run in the header, and left it switched off.

Nothing went live. The snippet sat there, saved but inactive, waiting for a human to flip it on.

This is the most sensitive item on the list. A bad snippet can break a whole site, not just one page. So even a routine thing like Google Analytics gets the same “show it, confirm it, then activate it” treatment as anything else.

10. Media Library Alt Text Audit

Missing alt text hurts two things at once: accessibility for screen-reader users and your image SEO. On a big site, hundreds of images can be missing.

MCP audits the whole library and proposes fixes in two phases. First it reports, then it writes, only after you approve.

Prompt to try:

Audit my WordPress media library for images with missing alt text. Work in two phases and write nothing in phase one. Find every image with no alt text, scan my posts for embedded images with empty alt, propose a short descriptive alt line for each, and show me the full list. Then stop and wait for me to confirm.

What happened: Phase 1 came back with a full inventory. 187 images in the library, split into two groups by priority.

The first group was 29 images actually used in live posts, the ones visitors and search engines see. Some already had alt text, and the agent marked those “Already set” instead of overwriting good data. Only the ones truly missing it got a proposed line.

The second group was 114 unused images sitting in the library, stock photos, avatars, and old design files. For these, it proposed short, plain descriptions based on what each image showed. A file named “cheerful-business-team-high-five” became “Business team members celebrating success with a high-five.”

Notice the proposed text describes the image simply, with no keyword stuffing. That matches W3C’s guidance on writing alt text, which says to describe what the image shows in context, not pack it with keywords.

Nothing was written to the site. The full report sat waiting for approval, exactly as asked.

Key Takeaways

• MCP can do more than publish posts. It can manage users, plugins, menus, comments, SEO data, code, and media.
• MCP shows what it plans to change before making most updates, so you can review the work first.
• Risky actions need your approval. Changes to user roles, plugin updates, and code do not happen without confirmation.
• MCP can spot issues that simple scripts may miss, such as duplicate menu names, similar CTAs, and missing or old meta descriptions.
• It does not overwrite content that is already correct, such as existing image alt text or post descriptions.
• Some checks depend on outside sources, so results may not always be complete.
• The safest approach is to review changes before they go live.

Final Thoughts

You can automate WordPress with MCP, not just writing or publishing posts. In these ten examples, it drafted content, managed users, checked plugins, cleaned up comments, fixed metadata, edited menus, added code, and audited a whole media library, all from prompts and all with a human review step before anything went live.

When you automate WordPress with MCP, it’s fast at finding and preparing work but asks before making important changes, giving you the speed of automation without giving up full control of your site.

Setting this up correctly takes care, especially on stores or client sites. If you’d rather have it configured properly from the start. WooNinjas offers WordPress AI Automation built with scoped access, review steps, and safe defaults. Talk to our WordPress team to get started today.

FAQs

What can you automate with WordPress MCP?

You can automate WordPress with MCP for content drafting, user and role management, plugin checks, comment moderation, SEO metadata, menu edits, code snippets, and media library alt text audits, all through plain-language prompts.

How can MCP automate WordPress tasks?

It connects an AI agent to your site through the WordPress REST API or a plugin, then runs read and write actions on your behalf, with a review step before anything changes.

What WordPress tasks can MCP handle?

Both content and admin work: drafting posts, listing users, checking plugin versions, editing menus, moderating comments, updating metadata, adding code, and auditing images for missing alt text.

Can WordPress MCP automate content updates?

Yes. It can draft posts, bulk-edit text across many pages, and update meta titles and descriptions, saving changes as drafts or showing them for approval before they go live.

Yes. With the right permissions, you can automate WooCommerce with MCP to read and update products, prices, and stock. We covered this in using MCP to update WooCommerce products.