Manage WordPress With Claude: WordPress MCP Tutorial

Manage WordPress With Claude: WordPress MCP Tutorial

Some links on this page are affiliate links. If you buy through one, we may earn a commission at no extra cost to you. It never changes a recommendation. How this works.

To manage WordPress with Claude over MCP, you install the official MCP Adapter plugin on WordPress 6.9 or newer, create an Application Password for a dedicated low-privilege user, and add your site’s MCP address to Claude Desktop or Claude Code. As of October 2026 the adapter is in the WordPress.org plugin directory, but it adds no AI features on its own: what Claude can do depends on which abilities your plugins make public.

This tutorial follows the MCP Adapter’s own documentation and WordPress.org’s docs, checked in October 2026; it does not include our own tests.

Most of what’s written about the adapter so far assumes you build plugins for a living. This wordpress mcp tutorial is the other version: for site owners and agencies who want to connect Claude to WordPress, run maintenance in plain English, and keep tight control over what the agent is allowed to touch.

What WordPress MCP actually does

MCP, the Model Context Protocol, is “an open standard for connecting AI agents to external systems,” in the words of the MCP Adapter’s plugin page. Instead of Claude guessing at your site through a browser, your WordPress install advertises typed capabilities, called abilities, such as “get site info” or “create a draft post.” Claude picks the ability; WordPress checks the connected user’s permissions before anything runs. If the protocol itself is still fuzzy, our plain-English primer on MCP servers for website owners covers it.

The practical difference from the old REST API workflow is discovery. With the REST API, you (or a developer) had to know every endpoint and wire it up by hand. With the adapter’s default server, Claude sees three tools when it connects: one lists the public abilities on your site, one reads an ability’s details, and one runs it. That is why a non-developer can do a wordpress mcp server setup without writing code. The catch: the adapter “does not provide any AI features itself.” Abilities come from WordPress core or from plugins, only abilities marked public can be reached over MCP, and if none are public yet, the list Claude sees is empty.

Step 1: Install the MCP adapter

Requirements first: WordPress 6.9 or newer (the Abilities API the adapter builds on is part of core from 6.9), a site served over HTTPS, and an administrator login. HTTPS matters because WordPress only offers Application Passwords on HTTPS sites, local development sites aside.

  • Update core. Dashboard > Updates. On 6.8 or earlier the adapter has nothing to plug into; the plugin lists WordPress 6.9 as its minimum.
  • Install the adapter. Plugins > Add New, search for “MCP Adapter”, click Install Now, then activate it. With WP-CLI: wp plugin install mcp-adapter --activate.
  • Note your endpoint. Your site’s MCP address is the Site Address (URL) from Settings > General followed by /wp-json/mcp/mcp-adapter-default-server. You’ll paste it into Claude shortly.
  • Add abilities. Install or activate a plugin that registers the abilities you want, or ask the developer of a plugin you already use whether it supports the Abilities API.

If the address returns a 404 or “rest_no_route,” check that the plugin is active and that your permalinks aren’t set to plain; on plain permalinks, the adapter’s guide says to use ?rest_route=/mcp/mcp-adapter-default-server instead. The same guide notes that some security plugins and hosts turn Application Passwords off, and some Apache setups strip the Authorization header before WordPress sees it.

Step 2: Create a scoped Application Password

Don’t connect Claude with your admin account. Create a dedicated user, named something like claude-agent so the audit trail is unmistakable, and give it the lowest role that can do the work. The adapter’s site owner guide suggests “Editor rather than Administrator” and says a separate user “keeps its actions easy to tell apart and easy to switch off.” Then generate an Application Password for that user under Users > Profile > Application Passwords. WordPress shows it only once, so store it in your password manager. The spaces in it are part of the format and can stay.

This one decision does more for your security than everything else in this guide combined. Every action runs with that user’s role, and per WordPress.org’s roles and capabilities table, an Editor can publish and manage posts and pages, moderate comments and manage categories, but can’t install or update plugins, edit theme files or create users. A badly worded prompt, or a compromised laptop, then has a hard ceiling on the damage it can do.

Step 3: Connect Claude Desktop or Claude Code

Both clients work; they connect differently. Claude Desktop reads MCP servers from a JSON file you open under Settings > Developer > Edit Config. The adapter’s guide adds an entry that starts a small helper, @automattic/mcp-wordpress-remote, which runs on your computer and passes Claude’s requests to your site. You need Node.js installed. The entry looks like this, with your own values:

{
  "mcpServers": {
    "wordpress-site": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
      "env": {
        "WP_API_URL": "https://example.com/wp-json/mcp/mcp-adapter-default-server",
        "WP_API_USERNAME": "your-username",
        "WP_API_PASSWORD": "your application password"
      }
    }
  }
}

Save the file and restart the app. Claude Code skips the helper and connects over HTTP: one claude mcp add --transport http command with your MCP address and an Authorization: Basic header made from your username and Application Password, joined by a colon and base64-encoded. Copy the exact command from the site owner guide rather than retyping it. Claude Code also runs non-interactively, so the same request can be scripted across several sites. The web version at claude.ai can’t connect on its own: it adds connectors through an OAuth sign-in, and WordPress doesn’t include an OAuth server.

Either way, run the smoke test the guide recommends: ask Claude to “List the WordPress abilities you can use on my site.” A list, or an answer that the list is empty, means the connection works. An error means it doesn’t. For a 401, check the username (the login name or email address, not the display name), check that the Application Password was copied in full and hasn’t been revoked, and ask your host whether the server passes the Authorization header to PHP.

Tasks to run first

Skip the party tricks. Once your plugins expose the matching abilities, these are the kinds of requests worth delegating in the first week. Check the list from the smoke test to see which your site supports today:

  • Draft and stage a post. “Write a short update announcing our new pricing, save it as a draft, and assign the News category.” You review in wp-admin, then publish. Claude drafts; you stay on the button.
  • Content audit. “List every post older than a year that has no internal links pointing to it.” A spreadsheet job becomes a request.
  • Bulk metadata cleanup. “Find posts missing a meta description and draft one for each.” Review the batch, approve, done.
  • Comment triage. “Summarize the pending comments and flag anything that looks like genuine customer feedback rather than spam.”
  • Plain-English queries. “Which categories have had no new posts this quarter?” The agent reads; you decide.

Notice what is not on the list: nothing destructive, nothing that publishes without review. That is deliberate. For the build side of the same idea, see our guide to whether Claude can build a website.

Scope what the agent can touch

The riskiest setup is full admin access on a production site on day one. This containment checklist follows the adapter’s own advice and WordPress’s role model.

  • Least privilege, always. Editor role for content work. Switch to a more powerful role only for a specific task, then switch back the same day.
  • Drafts by default. For the first month, instruct Claude to save everything as a draft. Publishing stays a human click.
  • Staging before production. The adapter’s guide says abilities “change your live site the same way an action in wp-admin does” and recommends trying new abilities on a staging copy first. Point the connection at staging and let it run there before you trust it with production.
  • Revoke without drama. Every Application Password is listed under Users > Profile with when it was last used, and Revoke cuts a client off at once. Create one password per client and device, and revoke the moment a laptop or contractor leaves the picture.
  • Backups before plugin work. If you do grant update rights, take a backup first and update one plugin at a time. Boring beats broken.

Hosting that won’t fight your agent

Your host affects how smooth this is. Some hosts and security plugins turn Application Passwords off, some server setups strip the Authorization header, and without staging every experiment happens on your live site. Four options:

Kinsta pairs well with this setup on paper: it routes traffic through Cloudflare with Enterprise DDoS protection, offers a REST API that Kinsta says is available to all customers while in beta, and starts at $35 a month for one site. Kinsta now operates on Oracle Cloud Infrastructure, which replaced its previous Google Cloud setup. The Kinsta API + Claude automation guide covers that pairing in depth.

WP Engine lists one-click staging and development environments on every plan, which is exactly where you want an agent living during its probation period, plus EverCache, which its plans page calls “WordPress-optimized caching.” Its entry plan costs $35 a month for one site, or $336 for the first year on annual billing (a new-customer price). If you use its Smart Search AI, which WP Engine says is “Powered by Model Context Protocol (MCP),” our Smart Search setup walkthrough covers it.

On a budget, Hostinger‘s Premium plan, at $2.99 a month on a 48-month prepay (renewing at $10.99), is a sane place to run your first experiments: spin up a throwaway WordPress install, connect Claude, and break things where it does not matter. Graduate to managed hosting when the agent graduates to production. Our best AI web hosting guide compares the options.

InstaWP builds this workflow into the host: its InstaMCP feature puts your WordPress site on an MCP server so you can point Claude or Cursor at it, according to InstaWP’s site. Every site starts as a sandbox, $2 a month per site, which is a safe place to test an agent, and moves to managed hosting from $5 a month per site when it goes live, billed by the day, per its pricing page.

Frequently asked questions

Do I need to know how to code to use WordPress MCP?

No. The adapter installs like any plugin. The most technical steps are pasting a JSON entry into Claude Desktop’s config file, with Node.js installed, or running one command in Claude Code. If you can install a caching plugin and follow copy-and-paste instructions, you can do this.

Is it safe to let an AI agent manage my WordPress site?

Safe is a spectrum you control. With an Editor account, drafts by default, and a staging site for anything risky, the blast radius is small. With an administrator’s Application Password on production and no backups, it is not safe at all. Every action runs with the connected user’s permissions, so the tooling is neutral; the scoping is the safety.

What is the difference between the WordPress MCP adapter and the REST API?

The REST API exposes endpoints that someone has to write integration code for. The MCP Adapter exposes abilities, each with a description and a JSON Schema for its inputs, in a format MCP clients understand, so Claude can discover what’s available the moment it connects. The adapter’s endpoint lives under /wp-json/ alongside the REST API, and both check the connected user’s permissions.

Can Claude update plugins through MCP?

Only if two things are true: a plugin on your site exposes a public ability that updates plugins, and the connected user’s role allows it. An Editor can’t update plugins (on a single site that capability belongs to administrators), which is why this guide starts there. When you are ready to delegate updates, grant the capability deliberately, back up first, and have the agent update one plugin at a time.

Last checked: October 2026. Prices and plans change; check the vendor’s page before you buy.

Want the guided version? Our free video courses are in production, starting with “Launch Your First Website with Claude.”