WordPress MCP: How to Connect AI Agents to Your Site (2026)

WordPress MCP lets an AI assistant like Claude or ChatGPT securely read and manage your WordPress site by talking to it through the Model Context Protocol (MCP). Instead of clicking around wp-admin, you ask the AI in plain language (“draft a post from these notes,” “find posts with broken links”) and it calls your site’s tools to do the work.

The official way to set this up is the WordPress MCP Adapter, which exposes your site’s registered “abilities” as MCP tools that any AI client can use. Managed hosts like Pressable also offer it with less setup.

This guide covers what MCP is, how WordPress connects to it, what you can actually do with it, how to set it up step by step, and the security rules that matter before you give an AI write access to your site.

What Is MCP (Model Context Protocol)?

The Model Context Protocol is an open standard introduced by Anthropic in late 2024 for connecting AI assistants to external systems. It has since been adopted across the AI ecosystem, including by OpenAI and Google.

The easiest way to picture it: MCP is a universal connector for AI, a bit like USB-C is for hardware. Before USB-C, every device had its own cable. Before MCP, every app needed its own custom AI integration.

With MCP, an application runs an MCP server that exposes a set of tools (actions the AI can take) and resources (data the AI can read). Any MCP-capable client, like Claude Desktop or Cursor, can connect to that server and use those tools. One protocol, any client, any service.

What Is WordPress MCP?

WordPress MCP is the bridge that turns your WordPress site into an MCP server, so AI assistants can interact with it through that same standard. Two pieces make it work.

The Abilities API. This is a WordPress framework where core, plugins, and themes register “abilities,” discrete actions like “create a post,” “search content,” or “update an SEO title.” It landed in WordPress core in 6.9, which is why that is the adapter’s minimum version, and it underpins WordPress’s native AI work (see the WordPress 7.0 AI framework). You do not install it separately: the standalone repository it was developed in has been archived now that the code is in core.

The WordPress MCP Adapter. This is the official package, maintained by WordPress.org contributors as part of the AI Building Blocks initiative, that bridges those abilities to the Model Context Protocol. It automatically converts a site’s registered abilities into MCP tools, resources, and prompts that an AI agent can discover and call, over HTTP or STDIO.

Worth knowing before you build on it: the adapter is at version 0.6.1, released 13 August 2026. It is pre-1.0 and moving quickly, its plugin header declares support for WordPress 6.9 through 7.1 and PHP 7.4 or newer, and it targets the 25 November 2025 revision of the MCP specification. That is not a reason to avoid it, but it is a reason to pin a version and read release notes: 0.6.1 exists solely because the 0.6.0 release ZIP was broken, and only people who installed from that ZIP were affected.

One note on the ecosystem, because a lot of older tutorials still point at the wrong thing. Automattic shipped an earlier standalone plugin, Automattic/wordpress-mcp, and it was archived in January 2026. Its own README now says it “will be deprecated as the mcp-adapter AI Building Block for WordPress continues releasing stable versions” and sends you to the official adapter. Its last release was v0.2.5 in July 2025 and the repository is read-only, so it will not receive security fixes. The Automattic and WordPress.org split trips people up well beyond MCP, and who actually owns WordPress explains which organisation controls which part of the project.

If you already have it installed, it is the plugin serving /wp-json/wp/v2/wpmcp and /wp-json/wp/v2/wpmcp/streamable, and it authenticated with JWT tokens or Application Passwords. Plan to migrate. If you are starting fresh, build on the official adapter and ignore any guide that tells you to install the Automattic plugin.

What You Can Do with WordPress MCP

Once your site is connected, you work with it conversationally through your AI client. The exact tools depend on which abilities are registered, but common ones include:

• Content operations: draft, publish, and update posts and pages, generate excerpts, or bulk-edit content from a prompt.
• Search and query: find posts by topic, status, author, or date without writing a REST API call yourself.
• Taxonomies and metadata: create or assign categories and tags, update SEO titles and meta descriptions.
• Maintenance: surface posts with broken links, thin content, or stale dates, then fix them.
• WooCommerce: query and manage products and orders, via the wc-mcp-ability package WooCommerce maintains. It is early-stage work rather than a finished product.

The key shift is that you stop translating your intent into clicks or code. You describe the outcome, and the agent calls the right tools to get there.

In practice it feels like a normal chat. Ask “find my five oldest posts about email marketing and tell me what each one is missing,” and the agent calls your search and read tools, then reports back. Approve a follow-up like “add an FAQ section to the first one,” and it drafts the change for you to review.

How to Set Up WordPress MCP

Before you start, you need three things:

• Runs on WordPress 6.9 or newer and PHP 7.4 or newer. 6.9 is where the Abilities API landed in core, and the adapter’s plugin header is tested up to WordPress 7.1.
• An Application Password for HTTP connections, and therefore a site served over HTTPS. WordPress hides Application Passwords entirely on sites that are not using SSL, which is the single most common reason this setup stalls before it starts. The adapter also supports JWT tokens and custom OAuth; WordPress.com’s own implementation uses OAuth 2.1.
• An MCP-capable AI client, such as Claude Desktop, Claude Code, Cursor, or another tool that supports MCP servers.

Option 1: The official MCP Adapter (recommended)

The adapter is not in the WordPress.org plugin directory, so you cannot find it by searching from your dashboard. There are two supported ways in. For developers, Composer:

# Install the official adapter via Composer
composer require wordpress/mcp-adapter

Otherwise, download mcp-adapter.zip from the Releases page of the GitHub repository and install it through Plugins > Add New > Upload Plugin like any other zip. That is the route the official announcement recommends for getting started quickly. Once active, it exposes your site’s registered abilities as MCP tools over HTTP or STDIO transport.

Option 2: Connect over STDIO with WP-CLI

The adapter ships WP-CLI commands, and this is the option most guides miss. If your AI client runs on the same machine as the site (local development, or a server you can reach over SSH), you can skip HTTP, Application Passwords and the proxy entirely and let the client run the site as a subprocess:

# See which MCP servers are registered
wp mcp-adapter list

# Serve the default server as a given user
wp mcp-adapter serve --user=admin

# Serve a specific server as a lower-privileged user
wp mcp-adapter serve --server=content-server --user=editor

The --user flag is the access control: the agent gets exactly that user’s capabilities, so pointing it at an editor account is the cleanest way to keep an agent away from settings and plugins. In a client config it looks like this:

{
  "mcpServers": {
    "wordpress": {
      "command": "wp",
      "args": [
        "--path=/path/to/your/wordpress/site",
        "mcp-adapter",
        "serve",
        "--server=mcp-adapter-default-server",
        "--user=admin"
      ]
    }
  }
}

For local work this is both simpler and safer than exposing an HTTP endpoint, because no credential ever leaves your machine.

Option 3: A managed host (Pressable)

If you would rather skip the setup, some managed hosts now offer MCP out of the box. Pressable’s is generally available and included with every plan at no extra cost, exposing 75+ tools to Claude Desktop, Claude Code, ChatGPT and Gemini CLI. Note what it covers, though: it is a hosting MCP, for creating sites, clearing caches, pulling backups, running WP-CLI and managing domains and SSL, rather than a replacement for the adapter’s content tools.

Option 4: Third-party MCP servers

A handful of community and commercial MCP servers for WordPress also exist, and unlike the official adapter some of them are in the plugin directory, which makes them the path of least resistance. Royal MCP is the most widely installed at the time of writing, with 10,000+ active installs and support for connecting Claude, ChatGPT and other assistants.

They can be a quick way to experiment, but vet any third-party tool carefully before connecting it: an MCP server with write access is effectively an admin-level integration, and you are trusting its author with your site. When in doubt, the official adapter is the safer foundation.

Connecting Claude (or Another AI Client) to Your Site

With the adapter installed, the connection comes down to authentication plus a small client config. The flow looks like this:

1. In WordPress, go to Users > Profile and create a new Application Password. Copy the generated password (you only see it once).
2. Add a new MCP server in your AI client and point it at your site. The official remote bridge (shown below) handles the connection.
3. Authenticate with your WordPress username and the Application Password you just created.
4. Restart the client. Your WordPress tools now appear in the AI’s tool list, ready to call.

For a remote site over HTTP, the adapter’s own CLI guide documents Automattic’s mcp-wordpress-remote proxy, launched with npx. It is a bridge rather than part of the adapter itself, but it is the configuration the official docs point at. The default MCP endpoint is /wp-json/mcp/mcp-adapter-default-server:

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

From there, you can ask the assistant to list its available WordPress tools, then start giving it real tasks.

Security: Read This Before You Connect

An MCP connection with write access can do anything its WordPress user can do. Treat setting one up like handing someone the keys to your admin. A few rules keep it safe:

• Use a dedicated user with the least-privilege role. Don’t connect as your main administrator. Create a separate user with the lowest role that still does the job: Editor for content work, Author if it should only touch its own posts.
• Prefer read-only when you only need analysis. If the agent is auditing content or pulling data, it doesn’t need write access at all.
• Use Application Passwords, not your login password. They are scoped, and you can revoke a single one the moment you’re done without changing your real password.
• Run over HTTPS only. An MCP endpoint with credentials should never be exposed over plain HTTP, and WordPress enforces half of this for you by hiding Application Passwords on non-SSL sites.
• Review before you automate. Start by approving the agent’s actions manually, only move toward unattended changes once you trust the workflow, and keep the ability to roll changes back.

WordPress MCP in the Real World

The ecosystem is young but already practical. A few examples of MCP connecting AI to WordPress sites and the services around them:

• Hosting control: Pressable’s MCP lets you create sites, manage backups, run WP-CLI and handle account tasks by talking to Claude, ChatGPT or Gemini CLI.
• Store management: WooCommerce maintains a wc-mcp-ability package that registers store operations as abilities for the adapter to expose. Treat it as something to watch rather than a finished integration.
• SEO data in plain language: RightBlogger, an AI blog automation tool that SmartWP’s author co-founded, ships a remote MCP connector that gives Claude, ChatGPT and other MCP clients access to your Google Search Console data, its keyword research, and the AI-visibility data from its AI Brand Monitor, which tracks whether ChatGPT, Gemini, Perplexity and Claude recommend your brand. In practice you ask for striking-distance keywords or CTR fixes in plain language, or ask which competitors an assistant names instead of you, with no API keys involved.
• Content maintenance: agents that audit a site on a schedule and fix broken links, missing internal links, and stale references over time.

One honest caveat from developers putting this to work in 2026: AI agents are most reliable on small, well-defined jobs. The early community consensus is that the more technical and self-contained the task (writing a snippet, debugging CSS, tagging and organizing content), the better the results, while full builds and anything ambiguous still need a human checking the work. MCP is powerful, but it works best paired with the human-approval step built into the protocol, not run as a hands-off autopilot.

Frequently Asked Questions

Wrapping Up

WordPress MCP turns your site into something an AI agent can operate directly: draft and publish content, query data, and handle maintenance, all through plain-language requests. The official WordPress MCP Adapter, reading the Abilities API that shipped in core 6.9, is the foundation, and managed hosts like Pressable make the hosting side easier to try.

Two practical notes before you begin. The adapter is pre-1.0 and not in the plugin directory, so install it deliberately and keep an eye on its releases. And if a guide tells you to install Automattic’s wordpress-mcp plugin, it predates January 2026; that project is archived.

It’s still early, so start small and lock down access: connect a dedicated least-privilege user with a revocable Application Password, begin read-only, and review actions before you automate them. For the bigger picture, see our guides to WordPress 7.0’s AI framework, the WordPress REST API, and the best WordPress AI plugins.