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 underpins WordPress’s native AI work (see the WordPress 7.0 AI framework) and ships with the MCP Adapter, which needs WordPress 6.9 or newer.

The WordPress MCP Adapter. This is the official package, maintained by the WordPress development team, 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.

One note on the ecosystem: Automattic shipped an earlier standalone plugin (Automattic/wordpress-mcp), but it is being folded into the official WordPress/mcp-adapter project. If you are starting fresh in 2026, build on the official adapter.

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: with the official WooCommerce MCP integration, query and manage products and orders.

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:

• WordPress 6.9 or newer, since the Abilities API and MCP Adapter depend on it.
• An Application Password for authentication (the adapter uses these for HTTP connections).
• 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 WordPress/mcp-adapter can be installed as a Composer package (the recommended path for developers) or as a traditional plugin. Once active, it exposes your site’s registered abilities as MCP tools over HTTP or STDIO transport.

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

If you would rather not use Composer, download the adapter as a plugin, upload it under /wp-content/plugins/, and activate it from the Plugins screen like any other plugin.

Option 2: A managed host (Pressable)

If you would rather skip the setup, some managed hosts now offer MCP out of the box. Pressable, for example, provides early access to WordPress MCP that connects Claude, ChatGPT, and Gemini directly to your hosting account, so you can spin up sites and manage content with AI and minimal configuration.

Option 3: Third-party MCP servers

A handful of community and commercial MCP servers for WordPress also exist. 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. 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.

Claude Desktop connects through the official remote bridge, launched with npx. A server entry looks like this (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.
• Review before you automate. Start by approving the agent’s actions manually. Only move toward unattended, automatic 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, and handle account tasks by talking to Claude or ChatGPT.
• Store management: the WooCommerce MCP integration exposes product and order operations to AI agents.
• SEO data in plain language: RightBlogger ships an MCP that connects Claude to your Google Search Console data, so you can ask for striking-distance keywords or CTR fixes without touching the GSC dashboard or an API key.
• Content maintenance: agents that audit a site on a schedule and fix broken links, missing internal links, and stale references over time.

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 (built on the Abilities API) is the foundation, and managed hosts like Pressable make it easier to try.

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.