AI Tools Tutorials 22 May 2026  ·  8 min read

Connect Claude to WordPress (2026): Full MCP Integration Guide

Connect Claude to WordPress (2026): Full MCP Integration Guide
Connect Claude to WordPress (2026): Full MCP Integration Guide 22 May 2026
TL;DR — Connecting Claude to WordPress now takes under 10 minutes: install two plugins (WordPress MCP Adapter + WDS MCP Content Manager), create an Application Password, and add a few lines to your AI client config. Your agent can then create posts, manage categories, and handle WooCommerce products through plain English — the connection is direct between your AI client and your server, so no content passes through Anthropic.

Connecting Claude to WordPress used to require custom REST API integrations, OAuth flows, and hours of developer time. In 2026, the Model Context Protocol (MCP) changes that completely: the full setup takes under 10 minutes, unlocks 50+ WordPress actions out of the box, and requires zero custom code. You install two plugins, paste a few lines of configuration into your AI client, and your entire WordPress site becomes a workspace your AI agent can read, write, and manage through plain English instructions — with no content passing through Anthropic’s servers.

This guide walks through every step in detail: what MCP is, why it matters, exactly how to install and configure it, what you can realistically do with it, and how to troubleshoot the issues that most people run into. Whether you are a content creator, a developer, a business owner managing a WooCommerce store, or an agency running cloud and DevOps workflows in Berlin, this tutorial covers your use case.

What Is the Model Context Protocol (MCP)?

The Model Context Protocol is an open standard published by Anthropic in late 2024. Its purpose is straightforward: it gives AI language models a structured, secure way to connect to external tools and data sources. Before MCP existed, every AI integration required custom code on both ends. A developer wanting Claude to interact with a database had to write a bespoke connector, handle authentication manually, and maintain the integration as both sides evolved. MCP standardises this entirely.

Think of MCP the same way you think of USB-C. Before USB-C, every device had a different connector. After USB-C, any compatible device works with any compatible cable. MCP is the USB-C of AI integrations: one protocol that any compliant AI client and any compliant server can speak to each other through, without custom code on either side.

For WordPress specifically, MCP works like this: a WordPress plugin exposes a set of abilities — named actions the AI can invoke, like wds/create-post or wds/update-product. Your AI client (Claude Desktop, Claude Code, Cursor) discovers those abilities automatically when you add the MCP server to its configuration. From that point on, when you ask Claude to create a post, it calls the ability directly rather than generating text for you to paste somewhere.

Why Connect an AI Agent to WordPress?

The obvious answer is speed. An AI agent that can write and publish a post in a single prompt is faster than writing in one tab, copying to another, adding categories, uploading an image, and setting metadata in a fourth. But speed is only part of the value.

The deeper value is that your AI agent now has context about your site. When you ask Claude to write a new post about a topic, it can first read your existing posts to understand your tone, check which categories already exist, and avoid duplicating content you have already published. When you ask it to update product pricing, it can read current prices first and confirm the change before making it. The AI is not just generating text — it is operating as an informed participant in your site’s content ecosystem.

For WooCommerce store owners, the productivity gains are particularly significant. Creating a product with pricing, description, downloadable files, and SEO metadata through the WordPress admin requires navigating four separate sections. Through MCP, the entire thing is a single prompt: “Create a digital product called X, priced at Y, with this description, and this download file.” The agent handles every field in one pass.

What You Need Before You Start

  • WordPress 6.3 or later running on a self-hosted installation. WordPress.com hosted sites do not support custom plugins and cannot use this setup.
  • Administrator access to your WordPress dashboard. You will be installing plugins and generating credentials.
  • An MCP-compatible AI client installed on your computer. Claude Desktop and Claude Code are the most common choices. Cursor and Windsurf also work.
  • Node.js installed on the computer running the AI client. Check by running node -v in a terminal. If it returns a version number, you are ready.

Step 1: Install the WordPress MCP Adapter

The WordPress MCP Adapter is the official plugin that creates the MCP endpoint on your site. It is maintained by the WordPress core team and published on GitHub at github.com/WordPress/mcp-adapter. The plugin registers a REST API route that speaks the MCP protocol, so AI clients can discover and call WordPress abilities through a standard interface.

  1. Go to WP Admin → Plugins → Add New Plugin
  2. Search for WordPress MCP Adapter and install it
  3. Click Activate

Step 2: Install WDS MCP Content Manager

Install it from WordPress.org:

  1. Go to WP Admin → Plugins → Add New Plugin
  2. Search for WDS MCP Content Manager
  3. Click Install Now and Activate
  4. Navigate to Settings → WDS MCP Setup to open the setup wizard

Step 3: Find Your MCP Endpoint URL

In Settings → WDS MCP Setup, click the Endpoint URL tab. You will see your full MCP endpoint URL:

https://your-site.com/wp-json/mcp/mcp-adapter-default-server

Step 4: Create a WordPress Application Password

  1. Go to WP Admin → Users → Profile
  2. Scroll to the Application Passwords section
  3. Enter a name like Claude Agent and click Add New Application Password
  4. Copy the password immediately — it is displayed only once

Step 5: Connect Your AI Client

Claude Desktop

{
  "mcpServers": {
    "wordpress": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
      "env": {
        "WP_API_URL": "https://your-site.com/wp-json/mcp/mcp-adapter-default-server",
        "WP_API_USERNAME": "your-wordpress-username",
        "WP_API_PASSWORD": "AbCd EfGh IjKl MnOp QrSt UvWx"
      }
    }
  }
}

Claude Code

claude mcp add wordpress
  --env WP_API_URL="https://your-site.com/wp-json/mcp/mcp-adapter-default-server"
  --env WP_API_USERNAME="your-wordpress-username"
  --env WP_API_PASSWORD="AbCd EfGh IjKl MnOp QrSt UvWx"
  -- npx -y @automattic/mcp-wordpress-remote@latest

Free Plan vs. Pro Plan: Full Comparison

Ability Free Pro
List and read postsYesYes
Create postsYesYes
Update postsYesYes
Get and create categoriesYesYes
Get and create tagsYesYes
Upload image from URLNoYes
Set featured imageNoYes
Create WooCommerce productNoYes
Update WooCommerce productNoYes
Inject JSON-LD schemaNoYes
Set Elementor page layoutNoYes
Set post language (Polylang)NoYes
Link translation pairs (Polylang)NoYes

Pro licenses are available at wallstrdev.com. A license key is delivered by email immediately after payment and activated under Settings → WDS MCP Setup → License.


Connecting Claude to WordPress through MCP is one of the more impactful workflow changes available to content creators and site owners in 2026. The setup is fast, the security model is sound, and the time savings compound significantly over time. For agencies and cloud engineering teams in Berlin running multiple WordPress sites as part of a DevOps pipeline, this integration provides the content automation layer for fully automated publishing workflows. Start with the free plan, confirm the workflow fits your process, and upgrade when the Pro abilities become relevant.