If you’ve ever wished you could manage your WordPress site through a simple conversation — creating posts, checking analytics, updating settings — without ever opening the dashboard, that wish is now a reality. The official WordPress MCP Adapter plugin makes it possible to connect WordPress to Claude Desktop and control your entire site using plain English. In this complete guide, you’ll learn exactly how to set up the WordPress MCP Adapter on WordPress 6.9+, configure Claude Desktop, and start managing your site through AI. Whether you’re a developer, content creator, or agency owner, this tutorial will get you up and running in under 30 minutes.
Table of Contents
What Is the WordPress MCP Adapter?
The WordPress MCP Adapter is an official plugin developed by the WordPress core team that bridges the WordPress Abilities API with the Model Context Protocol (MCP) — an open standard created by Anthropic. Rather than generating text that you then copy and paste into WordPress, Claude can call WordPress tools directly: creating a post, updating a page, retrieving plugin information, or adjusting site settings, all within a single conversation.
What Is the Model Context Protocol (MCP)?
MCP is an open standard that gives AI models a structured way to connect to external tools and services. Think of it as a universal plugin system for AI assistants. When those tools are WordPress operations, the result is an AI agent that doesn’t just suggest actions — it executes them. The protocol specifies how tools are discovered, how they’re invoked, and how results are returned, making it client-agnostic: Claude Desktop, Cursor, VS Code, and custom SDK clients all use the same adapter.
What Is the WordPress Abilities API?
Introduced in WordPress 6.9 as part of the AI Building Blocks initiative, the Abilities API allows plugins, themes, and core features to register discrete, named capabilities — called ‘abilities’ — that external agents can discover and invoke. The MCP Adapter converts these registered abilities into MCP tools, resources, and prompts that any MCP-compatible client can use.
Self-Hosted vs. WordPress.com
There are two main integration paths. WordPress.com-hosted sites have a built-in MCP connector that uses OAuth 2.1, available directly through Claude’s Connectors menu. Self-hosted WordPress.org sites — the focus of this guide — install the wordpress/mcp-adapter plugin and authenticate using WordPress Application Passwords. The official plugin is GPL-licensed, free to use, and available on GitHub.
Benefits of Connecting WordPress to Claude Desktop
Connecting your WordPress site to Claude Desktop through the MCP Adapter isn’t just a novelty — it unlocks a fundamentally different way to manage and scale your content operations. Here are the most impactful benefits:
Eliminate Dashboard Tab-Switching
With the MCP connection active, you can create, schedule, update, and optimize content without ever leaving your conversation with Claude. Instead of opening the WordPress editor, writing, then switching back to Claude for SEO suggestions, the entire workflow happens in one place. This alone saves hours per week for high-output content teams.
Natural Language Site Management
You can ask Claude to ‘create a draft post titled X, set the category to Y, and add these five tags’ — and Claude will do it. You can update SEO metadata, adjust page slugs, retrieve post IDs, and manage taxonomies through plain English requests. No documentation, no dashboard navigation, no manual form-filling.
Automate Repetitive Publishing Workflows
Content pipelines that previously required a developer — bulk post creation, metadata updates across multiple articles, scheduling content by date — become conversational tasks. Claude can execute multi-step WordPress operations in sequence, checking results between steps.
Reduce Human Error in CMS Operations
Manual WordPress admin work is error-prone: wrong categories, missed SEO fields, forgotten tags. Claude can apply consistent settings across every piece of content it creates, reducing the inconsistencies that accumulate over time.
WooCommerce and Plugin Integrations
The MCP Adapter can run alongside WooCommerce’s own MCP integration, meaning Claude can manage products, check order statuses, and update customer records in the same conversation where it’s also handling your blog content. Additional plugins that register their abilities to the WordPress Abilities API become instantly available to Claude without any extra configuration.
Future-Proof Your WordPress Stack
The Abilities API is now a first-class feature in WordPress core, and WordPress 7.0 has continued expanding native AI infrastructure. Connecting via the official MCP Adapter today means your workflow will naturally scale as more plugins and themes register abilities, without requiring you to reconfigure anything.
Prerequisites You Need Before Starting
Before you install the plugin or touch any config files, confirm that every item in this checklist is ready. Skipping prerequisites is the single most common cause of setup failures.
WordPress Requirements
- WordPress 6.9 or higher — the Abilities API is not available in earlier versions
- HTTPS enabled — Application Passwords require SSL; plain HTTP will cause auth failures
- Pretty permalinks enabled — go to Settings > Permalinks and choose any structure other than Plain
- REST API accessible — confirm your hosting does not block /wp-json/ requests
Local Machine Requirements
- js 18 or higher — run node –version to check
- npm — comes bundled with Node.js
- Claude Desktop — the desktop application, not the browser version
- Admin access to your WordPress site
Claude Desktop Version
Ensure you’re running a recent version of Claude Desktop that supports MCP server configuration. Navigate to Claude Desktop > Settings > Developer. If you see an ‘Edit Config’ button, your version supports MCP.
Step-by-Step Setup Guide
Follow these steps in order. Each step builds on the previous one — don’t skip ahead.
Step 1: Update WordPress to 6.9+
Log into your WordPress dashboard, navigate to Dashboard > Updates, and apply any pending WordPress core updates. The MCP Adapter requires the Abilities API, which shipped with WordPress 6.9. If you’re already on 6.9 or higher, proceed to Step 2.
Step 2: Download and Install the MCP Adapter Plugin
The MCP Adapter plugin is hosted on GitHub at WordPress/mcp-adapter. Download the latest release ZIP file from the Releases page. In your WordPress admin, go to Plugins > Add New > Upload Plugin, choose the downloaded ZIP file, and click Install Now. After installation completes, click Activate Plugin.
Note: The plugin registers a default MCP server endpoint automatically upon activation.
Step 3: Flush Permalink Rewrite Rules
After activating the plugin, navigate to Settings > Permalinks and click Save Changes without changing anything. This forces WordPress to re-register its rewrite rules and makes the MCP endpoint available at:
https://yoursite.com/wp-json/mcp/mcp-adapter-default-server
Visit this URL in your browser. If you see a JSON response (even an error message), the endpoint is live. A 404 means the rewrite rules haven’t flushed — repeat this step.
Step 4: Generate a WordPress Application Password
Application Passwords are scoped credentials that grant API access without exposing your main login password. To create one:
- Go to Users > Profile in your WordPress admin (or Users > All Users > edit your admin account)
- Scroll down to the Application Passwords section
- In the New Application Password Name field, type Claude MCP
- Click Add New Application Password
- Copy the generated password immediately — it’s shown only once and includes spaces (e.g., 2SEB qW5j D7CW fpsh pbmN RGva)
- Store it in a password manager — you’ll need it in Step 6
Step 5: Install the Automattic MCP Bridge Package
Claude Desktop communicates with the WordPress HTTP endpoint through a bridge npm package. Install it globally:
npm install -g @automattic/mcp-wordpress-remote
Verify the installation worked by running:
npx @automattic/mcp-wordpress-remote –version
If you see a version number, you’re ready. If you get a ‘command not found’ error, find your npm global bin path with npm bin -g and add it to your system PATH.
Step 6: Edit the Claude Desktop Config File
Open Claude Desktop. Navigate to Settings > Developer > Edit Config. This opens the claude_desktop_config.json file in your file browser. Open it in any text editor and add the WordPress MCP server configuration.
{
“mcpServers”: {
“wordpress”: {
“command”: “C:\\Program Files\\nodejs\\npx.cmd”,
“args”: [“-y”, “mcp-wordpress”],
“env”: {
“WORDPRESS_SITE_URL”: “https://yoursite.com”,
“WORDPRESS_USERNAME”: “your_admin_username”,
“WORDPRESS_APP_PASSWORD”: “xxxx xxxx xxxx xxxx xxxx xxxx”
}
}
}
}
Step 7: Restart Claude Desktop and Test
Fully quit Claude Desktop (don’t just close the window — use Quit from the menu or taskbar). Relaunch it. Claude Desktop reads the MCP config only on startup. Once restarted, open a new conversation and type:
List my 5 most recent WordPress posts
If Claude responds with actual post titles and IDs from your site, the connection is working. You should also see a small tool icon in the Claude interface indicating an active MCP server.
Configuration Files Explained
There are two transport options for the WordPress MCP Adapter: WP-CLI STDIO (for local development) and HTTP transport (for remote/production sites). HTTP transport is recommended for most users.
Demo Prompts to Try With Claude
Once your connection is live, these prompts give you an immediate taste of what’s possible. Each one exercises a different WordPress capability.
Content Creation Prompts
- “Create a draft post titled ‘Top 10 WordPress SEO Plugins in 2026’ in the SEO category with the tags: WordPress, SEO, plugins”
- “Write a 500-word introduction for a post about WooCommerce performance and save it as a draft”
- “Duplicate my most recent post as a draft with the title ‘Updated: [original title]'”
Site Information Prompts
- “List my 10 most recent published posts with their titles, IDs, and publish dates”
- “What plugins are currently active on my site?”
- “Show me all posts in the ‘Tutorials’ category that are still in draft status”
Content Management Prompts
- “Update post ID 142 to add the tag ‘beginner guide'”
- “Schedule post ID 155 to publish on Friday at 9am”
- “Find all posts with ‘WordPress’ in the title and list their current statuses”
Advanced Workflow Prompts
- “Create a 5-post content series on WordPress security: create all five drafts with placeholder titles, assign the Security category, and list their IDs when done”
- “Compare the SEO metadata of my last 3 published posts and suggest improvements”
Security Best Practices
Connecting an AI agent to your WordPress site is powerful, but it requires careful security hygiene. Follow these practices to keep your site safe.
Use a Dedicated, Limited Application Password
Generate a specific Application Password for Claude MCP — don’t reuse passwords from other applications. Name it clearly (e.g., ‘Claude MCP – Production’) so you can identify and revoke it instantly if something goes wrong. Application Passwords can be revoked from Users > Profile at any time without affecting your main login.
Run Claude as a Non-Admin User Where Possible
Create a dedicated WordPress user with the Editor role rather than Administrator for the MCP connection. Editors can create and manage posts but cannot install plugins, change themes, or modify core settings. This limits the blast radius of any unintended action.
Enable Tool-Call Approval in Claude Desktop
By default, Claude Desktop asks you to approve each tool call before it executes. Keep this enabled on production sites. The ‘Always allow’ toggle is convenient for development but should be treated with caution in live environments — especially for tools like create_post or update_settings.
Restrict the MCP Endpoint in Your Security Plugin
If you use a security plugin such as Wordfence, ensure the /wp-json/ path is not globally blocked. You can restrict it further by whitelisting only the IP addresses of machines running Claude Desktop if your IP is static.
Use HTTPS Only
Application Passwords transmitted over plain HTTP can be intercepted. Always ensure your WordPress site has a valid SSL certificate and that the WP_API_URL in your config file starts with https://.
Audit Regularly
Periodically review the Application Passwords listed under Users > Profile and revoke any you no longer use. Review posts and changes Claude has made by checking the WordPress revision history. The MCP Adapter does not bypass WordPress’s built-in audit trail.
Troubleshooting Common Issues
If your connection isn’t working, work through this section before concluding there’s a bug.
404 Error on the MCP Endpoint
This almost always means permalink rewrite rules haven’t been flushed. Go to Settings > Permalinks in your WordPress admin and click Save Changes. Then visit https://yoursite.com/wp-json/mcp/mcp-adapter-default-server again. If it still returns 404, confirm the plugin is active and that your permalink structure is not set to Plain.
Authentication Errors
Double-check three things: your WP_API_USERNAME matches your exact WordPress login username (not your display name or email), your Application Password was copied with all its spaces intact, and the user associated with the password has at least Editor-level access. Regenerate the password if you’re unsure.
REST API Blocked by Security Plugin
Wordfence, iThemes Security, and similar plugins sometimes block REST API requests. Check your security plugin’s firewall logs for blocked requests to /wp-json/. Whitelist the path or temporarily disable the security plugin to confirm it’s the cause.
Claude Desktop Not Showing the MCP Server
Claude Desktop reads the MCP config only on startup. Make sure you’ve fully quit the application — on Mac, use Cmd+Q or right-click the dock icon and choose Quit; on Windows, right-click the taskbar icon. After relaunching, a valid MCP connection will appear as a tool indicator in the interface.
Node.js or npx Not Found
Run npm bin -g in your terminal to find the global npm binary directory. Add that directory to your system PATH. On Mac, add export PATH=”$PATH:$(npm bin -g)” to your ~/.zshrc or ~/.bash_profile and restart your terminal session.
JSON Syntax Errors in Config File
The claude_desktop_config.json file is strict JSON. A missing comma, extra bracket, or misquoted value will prevent Claude Desktop from loading the config entirely. Paste the file contents into a JSON validator such as jsonlint.com to catch errors before restarting Claude.
Frequently Asked Questions
What is the WordPress MCP Adapter plugin?
The WordPress MCP Adapter is an official plugin that bridges the WordPress Abilities API with the Model Context Protocol, allowing AI agents like Claude Desktop to discover and invoke WordPress operations — such as creating posts, managing plugins, and reading site data — through a standardized protocol.
Does the MCP Adapter work with self-hosted WordPress?
Yes. The plugin is specifically designed for self-hosted WordPress.org sites running version 6.9 or higher. WordPress.com sites use a separate built-in connector with OAuth 2.1 authentication available directly through Claude’s Connectors settings.
Is the WordPress MCP Adapter plugin free?
Yes. The plugin is free and GPL-licensed. You only pay for your Claude Desktop subscription and your existing WordPress hosting. No Automattic subscription is required for self-hosted sites.
What authentication method does the MCP Adapter use?
For self-hosted sites, the adapter authenticates using WordPress Application Passwords — scoped credentials that grant API access without exposing your main admin password. Each password can be revoked independently without affecting your main login.
What WordPress version is required?
WordPress 6.9 or higher is required. The MCP Adapter depends on the Abilities API, which was introduced as a core feature in WordPress 6.9.
Can Claude Desktop publish posts on my WordPress site?
Yes. Once connected, Claude Desktop can create, update, schedule, and manage posts, pages, and custom post types through natural language. By default, Claude will ask for your approval before executing each action.
Is it safe to connect Claude to my WordPress site?
The connection is controllable. You choose which abilities are exposed, which user role Claude runs under, and Application Passwords can be revoked at any time. Claude Desktop prompts for tool-call approval by default. Avoid granting admin-level access in production environments.
Does the MCP Adapter work with WooCommerce?
Yes. WooCommerce ships its own MCP integration for product, order, and customer management. Both plugins can run on the same site simultaneously.
Conclusion
Connecting WordPress to Claude Desktop through the official MCP Adapter plugin is one of the most powerful upgrades available to WordPress professionals in 2026. With a 30-minute setup, you gain a conversational interface to your entire WordPress site — creating content, managing settings, querying data, and running multi-step workflows, all without touching the dashboard.
The combination of WordPress 6.9’s Abilities API, the official MCP Adapter plugin, and Claude Desktop marks a genuine shift in how WordPress sites can be managed. As more plugins register their abilities and the MCP ecosystem matures, the scope of what you can do in a single conversation will only expand.
Start with the setup steps in this guide, try the demo prompts in Section 6, and implement the security practices in Section 7. Once you’ve confirmed the connection is working, you’ll have a workflow that saves hours every week and scales naturally with your site.
→ Ready to connect your WordPress site to Claude Desktop? Start with Step 1 — update to WordPress 6.9 — and follow this guide from top to bottom. Your first AI-managed post is 30 minutes away.
