What Is a WordPress MCP Server?
A WordPress MCP server is a bridge that connects your WordPress website to AI agents like Claude, ChatGPT, and Cursor. It uses the Model Context Protocol (MCP) an open standard created by Anthropic to let AI assistants read, write, and manage your WordPress content through plain-English instructions.
Instead of clicking around wp-admin, you ask your AI assistant to create a post, update a page, or check your site settings. The AI calls your WordPress tools directly through the MCP server.
Think of it like a USB-C port for AI. Just as USB-C standardizes how devices connect, MCP standardizes how AI clients connect to external services including your WordPress site.
Why WordPress MCP Matters in 2026
WordPress powers 43% of all websites on the internet. As of 2026, every WordPress site running version 6.9 or higher has the infrastructure to support AI agents through MCP.
Here’s why this matters:
- Content automation: Create, edit, and publish posts using natural language
- SEO optimization: AI can audit your content, fix meta descriptions, and optimize for AI Overviews
- Site maintenance: Identify broken links, thin content, and stale pages
- E-commerce management: Query products, update inventory, and manage orders through WooCommerce
- Multi-site management: Control multiple WordPress installations from one AI interface
The WordPress core team shipped the Abilities API in version 6.9 (December 2025) and released the official MCP Adapter in February 2026. WordPress 7.0 (May 2026) made AI a headline feature of core.
How WordPress MCP Servers Work
WordPress MCP operates on a client-server model with three layers:
Layer 1: The Abilities API (WordPress Core)
The Abilities API is a registration system where plugins declare discrete actions they can perform. Each ability has:
- Input schema: What parameters the ability accepts
- Output schema: What data it returns
- Execute callback: The actual logic that runs
- Permission callback: Who can call this ability
Layer 2: The MCP Adapter (Official Plugin)
The WordPress MCP Adapter is the official plugin maintained by the WordPress development team. It bridges the Abilities API to the Model Context Protocol.
Layer 3: MCP Clients (AI Assistants)
Any MCP-compatible AI client can connect to your WordPress site:
- Claude Desktop and Claude Code
- Cursor (AI code editor)
- VS Code with GitHub Copilot
- ChatGPT (adding MCP support)
- Gemini (adding MCP support)
What You Can Do with WordPress MCP
Once connected, your AI agent can perform these actions through natural language:
Content Management
- Create, edit, and publish posts and pages
- Generate excerpts and summaries
- Bulk-edit content across your site
- Schedule posts for future publication
SEO and Metadata
- Update meta descriptions and title tags
- Optimize content for AI Overviews
- Fix missing alt text on images
- Audit internal linking opportunities
Site Maintenance
- Find posts with broken links or thin content
- Identify stale pages that need updates
- Monitor Core Web Vitals performance
- Check for crawl errors in Google Search Console
E-commerce (WooCommerce)
- Query product inventory
- Update product descriptions and pricing
- Manage order status
- Track customer data
Prerequisites: What You Need Before Starting
WordPress Version Check
Run this command in your terminal to check your WordPress version.
wp core version
Or check in wp-admin under Dashboard → Updates.
Node.js Installation
If you don’t have Node.js installed:
# macOS (using Homebrew) brew install node # Windows (using Chocolatey) choco install nodejs # Ubuntu/Debian sudo apt install nodejs npm
Verify installation:
node -v # Should return v18.0.0 or higher npm -v # Should return a version number
Step-by-Step Setup Guide
Step 1: Install the WordPress MCP Adapter
You have two installation options:
- Download the latest release from GitHub Releases
- In wp-admin, go to Plugins → Add New → Upload Plugin
- Upload the ZIP file and click Install Now
- Click Activate
The plugin automatically creates a default MCP server at:
https://your-site.com/wp-json/mcp/mcp-adapter-default-server
Option B: Install via Composer
cd /path/to/your/wordpress composer require wordpress/mcp-adapter
Then activate through wp-admin or WP-CLI:
wp plugin activate wordpress/mcp-adapter
Step 2: Create a Dedicated MCP User
⚠️ Security Warning
Never use your admin account for MCP connections. Always create a dedicated user with minimal permissions.
- Go to Users → Add New in wp-admin
- Create a new user with the Editor role (or Author for limited access)
- Note the username and password
For even tighter security, create a custom role using a mu-plugin:
Step 3: Generate an Application Password
For HTTP transport (remote sites), you need an Application Password:
- Go to Users → Profile in wp-admin
- Scroll to the Application Passwords section
- Enter a name like
MCP Agentand click Add New Application Password - Copy the password immediately — it’s shown only once
The password format includes spaces: xxxx xxxx xxxx xxxx xxxx xxxx
Step 4: Verify the MCP Endpoint
After installation, confirm the endpoint is live by visiting:
https://your-site.com/wp-json/mcp/mcp-adapter-default-server
You should see a JSON response describing the server. If you get a 404:
- Go to Settings → Permalinks
- Click Save Changes (without changing anything)
- Try the endpoint again
Step 5: Connect Your AI Client
Claude Desktop (HTTP Transport)
Edit your Claude Desktop configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add this configuration:
Claude Desktop (STDIO Transport - Local Development)
For local WordPress environments with WP-CLI:
Claude Code
Run this command in your terminal:
Step 6: Restart and Verify
- Fully quit and reopen your AI client (config is only read on startup)
- Look for a tools icon in the message input
- Click it to confirm
wordpressis listed with available tools - Ask your AI: “What WordPress tools do you have?”
The AI should return tools like
create_post, list_posts, get_site_settings, and more. Registering Custom Abilities
By default, the MCP Adapter only exposes abilities marked with meta.mcp.public => true. To add your own abilities, register them in a mu-plugin:
Restart your AI client after adding new abilities.
Security Best Practices
An MCP connection with write access can do anything its WordPress user can do. Treat it like handing someone the keys to your admin account.
1. Use a Dedicated User with Minimal Permissions
Never connect AI agents using your main administrator account. Create a separate user with only the capabilities the AI needs:
- Editor role: For content creation and editing
- Author role: For creating only their own posts
- Custom role: For specific, limited capabilities
2. Prefer Read-Only Access When Possible
If the AI is only auditing content or pulling data, it doesn’t need write access. Set the user’s role to Subscriber or create a read-only custom role.
3. Use Application Passwords, Not Login Passwords
Application Passwords are scoped and revocable. You can delete a single Application Password without changing your main login.
4. Run Over HTTPS Only
An MCP endpoint with credentials should never be exposed over plain HTTP. Use SSL/TLS on all production sites.
5. Review Before Automating
Start by approving the agent’s actions manually. Only move toward unattended automation once you trust the workflow, and keep the ability to roll changes back.
Troubleshooting Common Issues
“MCP server failed to start”
Cause: Node.js path issue or stale cache.
npx clear-npx-cache
Then restart your AI client.
"401 Unauthorized" When Claude Calls a Tool
Cause: Wrong Application Password, expired password, or deleted user.
Fix:
- Go to Users → Profile in wp-admin
- Generate a new Application Password
- Update the
WP_API_PASSWORDin your client config
"Tool Not Found" After Registering an Ability
Cause: Missing meta.mcp.public => true or wrong hook.
Fix:
- Ensure
meta.mcp.publicis set totrue - Verify you’re hooking on
wp_abilities_api_init, notinit
404 at the MCP Endpoint
Cause: Pretty permalinks disabled or rewrite rules not flushed.
Fix:
- Go to Settings → Permalinks
- Click Save Changes
- Try the endpoint again
WordPress MCP vs. REST API
MCP doesn’t replace the WordPress REST API ; it adds a standardised AI-agent interface layer on top of it.
Real-World Use Cases
Use Case 1: Content Pipeline Automation
Connect Claude to your WordPress site and create a content pipeline:
- Research: AI gathers information from the web
- Drafting: AI creates a post draft in WordPress
- Review: You approve or request changes
- Publishing: AI publishes the approved post
Use Case 2: SEO Audit Automation
Ask your AI agent to audit your site:
"List all posts published in the last 6 months that are missing meta descriptions. For each one, suggest a 150-character meta description based on the content."
Use Case 3: Multi-Site Management
Connect multiple WordPress sites to one AI client and manage them simultaneously:
"Check the last 5 posts on each of my three WordPress sites. Identify any that haven't been updated in over 6 months."
Use Case 4: WooCommerce Store Management
Connect Claude to your WooCommerce store:
"Show me the top 10 best-selling products this month. For each product, check if the description is over 200 words and suggest improvements."
The Future of WordPress MCP
- AI Client API: Provider-agnostic PHP interface for calling AI services
- Connectors API: Centralized management of AI provider connections
- Abilities API (JavaScript layer): Client-side abilities for browser-based AI
The WordPress core team is actively developing MCP integration. The official MCP Adapter will remain a separate package designed so if a new protocol replaces MCP tomorrow, the Abilities stay the same and only the adapter changes.
Get Your WordPress Site AI-Ready
Ready to connect your WordPress site to AI agents? Mid Hudson Web specializes in WordPress development and AI integration for businesses in the Hudson Valley and beyond.
Frequently Asked Questions
You need WordPress 6.9 or higher. The Abilities API that the MCP Adapter depends on was introduced in WordPress 6.9 (December 2025). WordPress 7.0+ provides the most complete AI foundation.
Yes. Any MCP-compatible AI client works, including ChatGPT, Claude, Cursor, and VS Code. The official WordPress MCP Adapter is client-agnostic connect whichever AI assistant you prefer.
It’s as safe as how you scope it. Use a dedicated user with minimal permissions, start with read-only access, run over HTTPS, and review actions before automating. Never connect AI agents with full admin privileges on production sites.
The WordPress MCP Adapter is free and open-source (GPL license). You only pay for your AI client subscription (Claude Desktop, ChatGPT, etc.) and your existing WordPress hosting.
Yes. WooCommerce ships its own MCP integration for product, order, and customer management. Install both the WordPress MCP Adapter and the WooCommerce MCP integration side by side for full e-commerce AI capabilities.
