Managing WordPress through AI isn’t a future concept — it’s happening right now. With the Model Context Protocol (MCP), Claude can go beyond generating text to directly executing WordPress operations: creating posts, managing plugins, configuring settings, and administering users through natural conversation.
The ecosystem has matured rapidly in early 2026. You now have three solid paths to connect Claude to WordPress, each suited to different setups. This guide covers all of them so you can pick the right one for your workflow.
What is WordPress MCP and Why It Matters
The Model Context Protocol is an open standard created by Anthropic that lets AI clients like Claude discover and invoke external tools. When those tools are WordPress operations, you get an AI assistant that doesn’t just generate content — it executes actions directly on your site.
The difference is significant:
Traditional AI Workflow
- AI generates content → You copy it → You paste into WordPress → You configure settings manually
MCP-Enabled Workflow
- You describe what you need → Claude executes it directly in WordPress
No context switching. No copy-paste. Structured confirmation built in. For developers and agencies managing multiple client sites, this transforms Claude from a content tool into a full operations multiplier.
3 Ways to Connect Claude to WordPress
Here’s a comparison of the three main approaches available in 2026:
| Method | Best For | Setup Time | Hosting | Supports Claude Code |
|---|---|---|---|---|
| WordPress.com Claude Connector | WordPress.com users wanting read-only AI analytics | ~2 minutes | WordPress.com (paid plan) | No (Claude Desktop/Web only) |
| Official MCP Adapter Plugin | Self-hosted sites wanting full control | 15-30 minutes | Any self-hosted WordPress | Yes (STDIO via WP-CLI) |
| InstaWP Managed MCP Server | Agencies, staging workflows, multi-site management | ~2 minutes | InstaWP cloud | Yes |
Let’s walk through each one.
Method 1: WordPress.com Claude Connector (Easiest)
In February 2026, WordPress.com became the first major WordPress host to offer a direct Claude connector — a one-click integration available from Claude’s connectors directory.
What It Does
The connector gives Claude read-only access to your WordPress.com site data via OAuth 2.1. Claude can:
- Summarize traffic metrics and reader engagement
- Identify outdated or unpublished content
- Analyze writing patterns and suggest topics
- Find broken links and internal linking opportunities
- Audit content for SEO gaps
It cannot create, edit, or delete content (yet). Think of it as giving Claude analyst-level access to your site.
Setup Steps
- You need a paid WordPress.com plan with MCP access enabled
- Open Claude Desktop or claude.ai → Settings → Connectors
- Click Browse Connectors and search for “WordPress.com”
- Click the + button and log in to WordPress.com
- Grant secured access via OAuth 2.1
- Start asking Claude about your site
That’s it. No API keys, no configuration files, no server setup.
Limitations
- Read-only — no content creation or management
- WordPress.com hosted sites only (not self-hosted)
- Requires a paid WordPress.com plan
Best for: WordPress.com users who want AI-powered analytics and content auditing without any technical setup.
Method 2: Official WordPress MCP Adapter (Self-Hosted)
The WordPress MCP Adapter is the official plugin developed by the WordPress core team. It bridges the new Abilities API (landing in WordPress core as of version 6.9) with the MCP protocol, letting AI agents discover and execute site functionality directly.
What It Does
Unlike the WordPress.com connector, the MCP Adapter provides full read-write access to your self-hosted WordPress site. It converts WordPress Abilities into MCP tools that Claude can invoke — posts, pages, users, plugins, themes, and anything registered via the Abilities API.
Requirements
- WordPress 6.7+ (6.9+ recommended for native Abilities API)
- WP-CLI installed (for STDIO transport)
- Node.js 20+ (for HTTP transport)
- Claude Desktop 0.9.2+ or Claude Code
- Application passwords enabled on your WordPress site
Setup: STDIO Transport (Local Development)
This is the simplest approach for local WordPress development environments:
- Install the MCP Adapter plugin from the GitHub repository
- Activate it in your WordPress admin
- Add this to your Claude Desktop config (
claude_desktop_config.json):
{
"mcpServers": {
"my-wp-site": {
"command": "wp",
"args": [
"--path=/path/to/your/wordpress",
"mcp-adapter",
"serve",
"--server=default",
"--user=admin"
]
}
}
}
- Restart Claude Desktop
Setup: HTTP Transport (Remote Sites)
For publicly accessible sites, you’ll need to set up a Node.js remote proxy:
- Install the MCP Adapter plugin on your WordPress site
- Create a WordPress application password (Users → Profile → Application Passwords)
- Configure the Node.js proxy to connect to your site’s MCP endpoint
- Point Claude Desktop or Claude Code to the proxy URL
Connecting Claude Code
Claude Code supports MCP servers natively. Add the server to your project’s .mcp.json or use:
claude mcp add my-wp-site -- wp --path=/path/to/wordpress mcp-adapter serve --server=default --user=admin
This is particularly powerful for developers who want to manage WordPress from the terminal alongside their code.
Limitations
- Requires technical setup (WP-CLI, Node.js)
- You manage the infrastructure and authentication yourself
- Abilities must be explicitly flagged for MCP access
Best for: Developers with self-hosted WordPress sites who want full control and don’t mind the initial setup.
Method 3: InstaWP Managed MCP Server (Recommended for Agencies)
InstaWP solved the biggest friction point with WordPress MCP: setup complexity. They built MCP directly into their managed WordPress platform — no external servers, no configuration files, no command line required.
When you enable MCP on an InstaWP site, three things happen automatically:
- The WordPress MCP plugin installs on your site
- A secure authentication token generates instantly
- Your unique MCP endpoint URL becomes available
Total time: under two minutes.
Why InstaWP’s Approach Stands Out
Zero Infrastructure Management
The MCP server runs on InstaWP’s infrastructure. You’re not spinning up Node.js processes, managing ports, or debugging connection issues. It simply works.
Built-in Staging Safety
This is crucial for agencies. InstaWP sites are sandboxed environments by default. If Claude executes something unexpected, you haven’t touched a live client site. Reset and retry — zero consequences.
Visual Token Management
Generate role-specific tokens from a dashboard interface. Create an Editor-level token for content operations. Create a separate Admin token for plugin work. Set expiration dates. Revoke access instantly. All without editing configuration files.
Multi-Site Dashboard
Agencies don’t manage one site — they manage dozens. InstaWP lets you enable and manage MCP across all your sites from a single dashboard. Each site gets its own token, permissions, and access controls.
Pre-Built WordPress Tools
InstaWP’s MCP server exposes comprehensive WordPress functionality out of the box:
- Content operations (posts, pages, custom post types)
- Taxonomy management (categories, tags, custom taxonomies)
- Media handling (uploads, featured images, metadata)
- User administration (create, update, role assignment)
- Comment moderation
- Plugin and theme management
- Site settings and options
No custom development required to start being productive.
Step-by-Step Setup
Step 1: Create Your WordPress Site
Go to instawp.com and log in (or create a free account). Click “Create New Site” from your dashboard. You have multiple options: From Scratch, From Snapshots, From Store, or From AI.
Configure your preferences (WordPress version, PHP version, site name), select a pay-as-you-go managed hosting plan, and click Create. Your WordPress site is live in roughly 30 seconds.
Step 2: Enable the MCP Server
In your InstaWP dashboard, click on your site to open Site Details and find “MCP” in the left sidebar menu. Click “Enable WordPress MCP Server.”
InstaWP automatically:
– Installs the WordPress MCP plugin
– Generates your secure authentication token
– Activates the MCP endpoint
Step 3: Copy Your MCP URL
Your unique MCP URL appears in the dashboard. Click the copy button to grab the complete URL.
Step 4: Connect Claude Desktop
Download Claude Desktop if you haven’t already. Open Claude and navigate to Settings → Connectors.
Click “Add Custom Connector” and paste your InstaWP MCP URL. Enter a descriptive name (e.g., “Client – Acme Corp” or “Staging – Project X”) and click Add.
Step 5: Connect Claude Code (Optional)
If you prefer working from the terminal, add the InstaWP MCP URL to your project’s .mcp.json:
{
"mcpServers": {
"client-site": {
"type": "url",
"url": "YOUR_INSTAWP_MCP_URL"
}
}
}
Step 6: Start Working
Open a new Claude conversation and test:
“List all posts on my WordPress site”
Claude queries your site via MCP and returns a formatted list of posts with titles, IDs, status, and dates.
Best for: Agencies managing multiple client sites who want zero-friction setup with built-in staging safety.
Real-World Use Cases
Once Claude is connected to your WordPress site, abstract AI capabilities become concrete operational workflows:
| Use Case | Task | Example Prompt |
|---|---|---|
| Client Onboarding | Create standard site structure | “Create pages: Home, About, Services, Contact, Blog. Add categories: News, Tutorials, Case Studies. Create a welcome post draft.” |
| Bulk Content | Schedule posts in batches | “Create 8 draft posts with these titles for March. Assign to ‘Seasonal’ category, tag with ‘spring-2026’, schedule for Mondays and Thursdays.” |
| Content Audit | Find and organize stale content | “List all posts in ‘Uncategorized’ and suggest appropriate categories based on their titles.” |
| Security Audit | Check plugin health | “List all active plugins with versions. Flag any not updated in 12 months or removed from the repository.” |
| Plugin Management | Bulk plugin actions | “Deactivate all plugins except WooCommerce, Yoast, and Wordfence.” |
| Team Setup | Create user accounts | “Create editor accounts for these 5 email addresses with temporary passwords.” |
| SEO Analysis | Review content for optimization | “Review all published posts from the last 6 months. Flag posts with titles under 40 characters or missing featured images.” |
Each of these tasks would typically require multiple clicks, page loads, and context switches in wp-admin. With MCP, they become single-prompt operations.
Security Best Practices
Regardless of which method you choose, follow these guidelines:
- Use role-specific tokens — Create Editor-level tokens for content operations and separate Admin tokens for plugin/theme work. Never use a superadmin token for routine tasks.
- Test on staging first — Especially for write operations. InstaWP’s sandboxed environments or WordPress’s built-in staging capabilities let you validate workflows before touching production.
- Set token expiration dates — Don’t leave permanent access tokens active. Rotate them regularly.
- Review before publishing — Use Claude to create drafts, not published posts. Always review AI-generated content before it goes live.
- Use application passwords — For the MCP Adapter method, WordPress application passwords provide scoped API access without exposing your main login credentials.
What’s Coming Next
The WordPress + AI integration space is evolving fast:
- WordPress 7.0 will include native AI infrastructure as a core component — not a plugin, not a third-party dependency
- The Abilities API is landing in WordPress core (v6.9), making MCP integration a first-class citizen
- Claude Cowork, a new plugin from Automattic, can build entire WordPress block themes from conversation
- Expect write capabilities in the WordPress.com Claude Connector soon
This isn’t a trend — it’s the new infrastructure layer for WordPress development.
Frequently Asked Questions
Which method should I choose?
If you’re on WordPress.com and want quick analytics access, use the Claude Connector. If you run self-hosted WordPress and want full control, use the official MCP Adapter. If you manage multiple client sites and want the fastest setup with staging safety, use InstaWP’s managed MCP server.
Does this work with Claude Code or just Claude Desktop?
The official MCP Adapter and InstaWP both work with Claude Code (the terminal-based AI coding tool). The WordPress.com connector currently only works with Claude Desktop and claude.ai. Claude Code is especially useful for developers who want to manage WordPress alongside their codebase.
What WordPress operations can Claude perform?
With the MCP Adapter or InstaWP: full content management (posts, pages, custom post types), taxonomy operations, media uploads, user management, comment moderation, plugin/theme management, and site settings — essentially anything accessible via the WordPress REST API. The WordPress.com connector is currently read-only.
Does this work with ChatGPT or other AI tools?
MCP is an open protocol. While Claude has native MCP support, other MCP-compatible clients like Cursor, VS Code Copilot, and Windsurf can also connect. The WordPress.com connector is Claude-specific.
Is my data shared with Anthropic?
No. Your credentials authenticate between the MCP server and your WordPress site. Content passes through during your conversation for context but is not stored or used for model training.
Can I connect multiple WordPress sites to one Claude session?
Yes. Add each site as a separate connector in Claude Desktop or list multiple servers in your .mcp.json for Claude Code. Reference them by name in your prompts: “List posts on client-alpha” or “Create a page on staging-beta.”
What if Claude does something I didn’t intend?
Use staging environments (InstaWP’s sandboxed sites or your own staging). For production, use role-limited tokens (Editor instead of Admin), and leverage WordPress’s built-in revision system and Trash recovery. InstaWP also offers instant site resets.
How is the MCP Adapter different from InstaWP’s MCP server?
The MCP Adapter is an official WordPress plugin that runs on your own server — you manage the infrastructure, authentication, and updates. InstaWP’s MCP server is a fully managed service where everything is handled for you, plus you get a multi-site dashboard and visual token management. Think of it as self-hosted vs. managed hosting.