How to Connect Claude to Your WordPress Site with MCP
You’re deep in a conversation with Claude about your content strategy. You’ve mapped out the next three months of blog posts, settled on topics, even talked through ideal lengths and keyword angles. And then you close the chat, open a browser tab, log in to WordPress, navigate to Posts, click New, and start typing.
The gap between “decided what to do” and “actually doing it” is exactly where AI assistants lose momentum — and it’s a solved problem. The Model Context Protocol lets Claude reach directly into your WordPress site. No copy-pasting. No tab-switching. Just: “Create a draft post called X with this content.”
What is MCP?
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external systems. Think of it like USB for AI tools: a standardized interface that lets any compatible AI agent (Claude, Cursor, Windsurf, or local models) communicate with any compatible service.
Before MCP, connecting AI to external systems meant writing custom integrations for each combination — Claude + WordPress, GPT + Shopify, Gemini + Notion. Every integration was a one-off. MCP replaces that mess with a single standard: the AI assistant connects to an MCP server, the server exposes tools, and the assistant calls those tools.
WordPress already has a solid REST API. MCP is the bridge that lets AI agents use it properly, with typed inputs, structured outputs, and error handling that makes sense to an AI.
The WordPress + MCP Combination
Once your WordPress site is connected via MCP, Claude can do work that previously required you to be logged into the admin panel. Practically, this means:
- Content management: List your recent posts, create new drafts, update existing content, change publish status — all from within a Claude conversation.
- WooCommerce operations: Query your product catalogue, update prices, modify descriptions, check stock quantities.
- Site inspection: Pull your site title, tagline, and settings without opening a browser.
The real value is how it fits into a workflow. You’re discussing a product launch with Claude. It can immediately check what products you have, what their current prices are, draft updated descriptions, and push those as pending changes — all in the same conversation, without you touching the WordPress admin.
Get Early Access
The WordPress MCP Server is currently in private early access. We’re onboarding users in batches to make sure setup is smooth.
Tell us what you’re building and we’ll send you access details.
What You Can Do Now
Here are concrete examples of what this enables, with the kind of responses you’d actually get:
Check your recent content:
“Show me my last 5 published posts”
Claude queries the WordPress REST API and returns: titles, publish dates, slugs, and word counts. You can immediately ask follow-up questions — “which of these has the lowest word count?” — without leaving the conversation.
Create content without switching tabs:
“Create a draft post titled ‘Five Things We Learned Shipping Our First Plugin’ with this content: [paste your outline or draft]”
Claude calls create_post with status draft. The post appears in your WordPress admin instantly, ready for you to review and publish.
Manage WooCommerce products:
“What products do I have under $50?”
Claude lists all products, filters by price, and returns the matching items with IDs, names, and current prices.
“Update product 42 price to $34.99 and change the description to: [your new text]”
Claude calls update_product with the new values. Done.
Inspect your site config:
“What is my site’s tagline and what WordPress version is it running?”
Claude calls get_site_info and pulls the data from the API root. No admin login required.
Where This Is Going
MCP is still early. The tooling is rough, the documentation is scattered, and most platforms don’t have well-maintained servers yet. But the pattern is clear: AI assistants will increasingly operate business systems directly, not just advise on them.
The WordPress MCP Server is the first step toward an AI assistant that can genuinely manage a site — not just describe what you should do, but do it. The next steps are tighter WooCommerce integration, permission controls (what can this agent touch?), and Shopify support.
The WordPress MCP Server is currently in private early access. Request access → or reach out at hello@axtolab.com if you want to contribute.