Talk to your WordPress site: content, SEO, WooCommerce, page builders, media and speed, with undo.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON ▾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for WordPress MCP, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Documentation Overview
WordPress MCP
Turn any WordPress site into a remote MCP server that any AI assistant can read, see, and work on directly, with an undo button.
Engine-agnostic SEO (Yoast / Rank Math) · AEO/GEO (JSON-LD, llms.txt, robots, redirects, IndexNow) · complete WooCommerce store operations · page-builder aware editing · site speed auditing and optimisation · live Search Console / GA4 / PageSpeed, all over one authenticated endpoint.
Works with every AI client that speaks MCP
 Claude |  ChatGPT |  Codex |  Gemini CLI |  Cursor |  VS Code |  Windsurf |  Zed |  Cline |  Any MCP client |
🔌 One endpoint, every AI client
WordPress MCP speaks the open Model Context Protocol over standard Streamable HTTP. It isn't tied to any one AI vendor. Install it on a client site and connect whichever assistant you or your team use: Claude, ChatGPT, Codex, Gemini, Cursor, Copilot, or all of them at once. The settings screen generates a ready-to-paste config for each one. The agent can then see the real site and implement changes itself. No copy-paste, no second OAuth, no guessing which SEO plugin the client runs.
Table of contents
- What it does
- Quick start
- Connect your AI client
- Prompts, resources, search and fetch
- Sign in with WordPress (OAuth)
- Teams, clients and approvals
- Health checks and the connection test
- WP-CLI
- Structured output and live progress
- MCP Registry
- Who it's for
- Why it exists
- What makes it different
- Architecture
- Request lifecycle (the wire)
- Safety: dry run, undo, audit
- Error handling
- Capability model
- Tool catalogue (165)
- Media and images
- Page-builder editing
- Commerce operations
- Engine-agnostic SEO layer
- Technical SEO: links, sitemaps, IndexNow
- AEO / GEO layer
- Performance layer
- Editing WordPress from a coding agent
- Google Site Kit bridge
- Security model
- Protocol compliance
- Workflow: how an agency uses it
- Extending
- Release history
- License
What it does
One plugin, one endpoint, 165 typed tools, plus ready-made prompts and browsable resources. Any MCP client connects once per site and can then do the whole job rather than describe it:
| 📊 Read the real site | What is published, which SEO engine runs, what schema exists, what Search Console actually reports, what is slow, what is out of stock. |
| 👁️ Look at the images | get_image_bytes returns a picture, not a filename, so alt text and product copy come from what is in the photograph. |
| ✍️ Write to the live site | Meta through whatever SEO plugin the client runs, JSON-LD, posts, products, prices, stock, menus, widgets, theme files. |
| 🧩 Edit builder pages safely | Elementor, Gutenberg, Divi and WPBakery pages are edited in their own data structure, not by flattening post_content. |
| 🛒 Run the store | Catalogue, variations, images, bulk repricing, scheduled sales, inventory and coupons. Orders and customer data sit behind their own switch. |
| 🚀 Make the site faster | Audit, apply reversible front-end fixes, clean the database, and prove the change with real Core Web Vitals. |
| ↩️ Take it all back | Writes are journalled. Every change returns an operation_id; one call reverses it. |
Quick start
- Upload the ZIP from Releases via Plugins → Add New → Upload Plugin, or copy the folder to
wp-content/plugins/wordpress-mcp/. - Activate WordPress MCP.
- Open WordPress MCP in the admin menu. Under Connect an AI client, pick your client and copy the snippet. The site's real endpoint and key are already filled in. Claude and ChatGPT need only the URL: you sign in with WordPress when they ask.
- Click Test connection to confirm AI clients can get through. It catches stripped headers, firewalls and caches.
- Toggle the capability groups you need. The defaults are safe. To give someone else access, create a connection key with a preset instead of sharing yours.
Then ask for something real:
"Audit this site's SEO, show me the ten worst pages, and fix the missing meta descriptions."
Requires WordPress 5.6+ and PHP 7.4+. WooCommerce and Google Site Kit are optional. Their tools appear only when those plugins are active.
Connect your AI client
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about WordPress MCP
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/wordpress-mcp-2)HTML Embed
<a href="https://allmcps.com/mcp/wordpress-mcp-2"><img src="https://allmcps.com/api/badge/wordpress-mcp-2?style=directory" alt="WordPress MCP on AllMCPs" /></a>