There is no single best WordPress MCP server in 2026, because they solve different problems. If you are on WordPress.com, use its built-in MCP. If you are a developer building custom abilities, use the official WordPress MCP Adapter. If you want content, SEO and store operations handled in one place without writing code, a full connector like wptaskify covers the most ground. This guide tests each one and tells you which fits your case.
A quick disclosure before we start
Full disclosure: I build one of the tools on this list (wptaskify). I have tried to be straight about where it wins and where it does not. You will see it lose a few categories below.
At the end of 2025 the WordPress MCP space was practically empty. By mid 2026 there are more than six real options, and they are aimed at very different people. I connected each of these to a live site (not a sandbox) and put them through the same tasks: list posts, write and publish an article, fix on-page SEO, and where possible touch a product. This is what I found.
First, what a WordPress MCP server actually is
MCP stands for Model Context Protocol. It is an open standard that lets an AI client, such as Claude or ChatGPT, call an external service's tools through a clear contract. Instead of the AI guessing at REST API calls, the service declares exactly what it can do, and the AI calls those tools when you ask.
A WordPress MCP server is the piece that exposes your site's abilities (create a post, upload an image, edit SEO) as tools. The MCP client is your AI app that uses them. This is where most people get confused: you install or enable a server on the WordPress side, then add its link to your AI client on the other side.
The key point is that MCP does not just make the AI write text. It lets the AI act: publish, edit, optimize, upload. The difference in practice looks like this:
- Before: ask ChatGPT for an article, copy it, open WP admin, paste, format, fill the meta fields, publish.
- After: "Write and publish an SEO post about X." Done.
If you have not connected a site yet, our step-by-step guide to connecting WordPress to Claude or ChatGPT walks through the whole flow.
The 2026 landscape at a glance
Here is the quick comparison. Where a tool count could not be verified, it is listed as "varies" on purpose, because a wrong number would be worse than an honest one.
1. WordPress MCP Adapter (the official one)
This is the official server, built on the WordPress Abilities API that shipped in WordPress 6.9. It is part of the WordPress AI Building Blocks initiative, and the Abilities API is on track to merge into WordPress 7.0 core. In other words, this is the foundation the rest of the ecosystem is being built on.
What is good:
- Vendor-neutral, free and official.
- Any plugin can register its own abilities, so the surface area grows with the ecosystem.
- Long term, this becomes the shared base layer that other tools sit on.
What is not:
- Setup is developer-level: GitHub releases, Composer, config files.
- The bare adapter ships with very few abilities. To make it useful you register your own.
- It is not practical for a non-technical user today.
Verdict: if you are a developer building custom abilities, this is the right place. It is a foundation, not a finished product. It is not a competitor to the hosted connectors so much as the layer beneath them. You can read the official details on developer.wordpress.org and the code on github.com/WordPress/mcp-adapter.
2. WordPress.com MCP
WordPress.com ships MCP built into its paid plans. There is no plugin to install. It exposes 60 or more curated tools and authenticates with OAuth 2.1, which means you never share a password and can revoke the token at any time.
What is good: setup is effectively nothing, and the security model is the cleanest of the bunch. Token-based auth you can revoke beats copying an application password around.
What is not: it only works on WordPress.com. Self-hosted sites get nothing here. The tool set is curated rather than exhaustive, so deep SEO work or store operations are limited.
Verdict: if you are on WordPress.com, use this and stop looking. See the docs at developer.wordpress.com/docs/mcp.
3. InstaWP MCP
InstaWP offers a managed MCP that you switch on with a toggle. It is integrated with staging environments, so there is no Node.js setup and no application password to manage.
What is good: this is the best option for testing. Trying an AI workflow on a sandbox before you point it at a client's live site is genuinely smart, and InstaWP is built exactly for that.
What is not: its primary focus is the dev and staging workflow, not ongoing content operations. It is a place to experiment, not a production content engine.
Verdict: reach for InstaWP to test AI workflows safely. For a day-to-day content and SEO engine, it is not the target.
4. seowriting.ai MCP
seowriting.ai provides a content-focused MCP plugin. You install it and connect your AI client, and it is purpose-built for generating articles.
What is good: it is built for content, so if writing articles is the whole job, it does that job well.
What is not: the scope stops at content. Technical SEO, store management and file editing are outside what it does.
Verdict: fine if you only need articles. If you also need meta, schema, internal links, products or backups, you will outgrow it.
5. Open source options (docdyhr/mcp-wordpress and others)
There are several community MCP servers on GitHub and mcpservers.org. They are free, self-hosted, and give you full control of the code.
What is good: zero cost and the code is yours to read and change.
What is not: you are the maintainer. If something breaks, you fix it. Updates and security are your responsibility.
Verdict: if you are comfortable in a terminal and have the time, this is the most flexible option. If you want something that just works, it is not the easy path.
6. wptaskify
This is the tool I build, so read this section with that in mind. wptaskify is a hosted connector with 280 tools spanning WordPress, WooCommerce and Shopify. It uses a bring-your-own-AI model: you connect your own Claude or ChatGPT, so there is no second AI subscription. There is a free plugin and a free MCP tier.
What is good:
- The widest tool coverage here, especially store operations and technical SEO.
- It connects to Google Search Console, Google Analytics and Bing, so the AI works from your real data.
- An approval inbox and automatic backups before file edits.
- Setup is about two minutes and needs no code.
What is not (honestly):
- It is in active development and ships often, so things change under you.
- 280 tools are overkill if all you want is to publish blog posts.
- It is a hosted service, not vendor-neutral like the official adapter.
- The ecosystem is new and not as battle-tested as the official adapter yet.
Verdict: if you want content, SEO and store handled in one place without writing code, this is the most complete option. If you only ever publish drafts, it is more than you need. You can see the full list of 280 tools if you want the exact surface area.
Which one should you actually pick?
Skip the marketing and match the tool to your situation.
- On WordPress.com? WordPress.com MCP. Do not look further.
- Developer building custom abilities? The official WordPress MCP Adapter.
- Testing AI workflows safely first? InstaWP.
- Comfortable in a terminal, want free, can maintain it? Open source (docdyhr/mcp-wordpress).
- Just want articles? seowriting.ai or wptaskify Free.
- Content, SEO and store in one place, no code? wptaskify.
What to check before you connect any MCP server
Whichever one you pick, run through this list first. It saves the most common surprises.
- Write access. Can the server only read, or can it write too? Some connectors have been read-only in certain clients. Do not assume.
- Auth method. Application Password versus OAuth. OAuth is safer because you can revoke it without changing your login.
- Approval flow. Will the AI publish directly, or do you approve changes first? For a live site, an approval step is worth having.
- Backups. Does it back up a file before editing it? File edits without a backup are how sites break.
- Scope creep. More tools means more surface area. Do not grant more permissions than the job needs.
Practical advice: do not point a brand-new MCP server at a production site on the first try. Test on staging. If you hit a wall, our notes on 401 and 403 connection errors cover the usual causes. Once you are set up, you can also auto-publish AI articles and make sure your content is written to get cited by AI search engines.
The short version
The WordPress MCP space is moving fast. The official adapter is becoming the foundation, and the purpose-built tools each solve a specific workflow. Pick the one that matches your situation rather than the one with the loudest pitch.
If you want the store, SEO and content side handled without writing code, wptaskify has a free tier. Connect a site and try it.
Frequently asked questions
Do I need WordPress 6.9 for MCP?
For the official adapter, yes, because the Abilities API it uses is in core from 6.9. Third-party servers use their own REST API integration, so they work on older versions too.
Is MCP free?
The protocol is free. Servers price differently: the official adapter is free, WordPress.com MCP is on paid plans, and the rest are freemium or free with a paid upgrade.
Can Claude publish directly to WordPress?
Yes, if the server exposes write tools and you have set up authentication. Claude then creates and publishes posts on your instruction.
Do I need a separate AI subscription?
It depends on the tool. Some sell their own AI and charge credits. Bring-your-own-AI connectors let you use your existing Claude or ChatGPT, so there is no second AI bill.
Is it safe to give AI write access to a live site?
With approval flows and backups, yes. Without them, test on staging first before you let an AI change a production site.
Related guides
Run content, SEO and your store from your own AI, free to start
Bring your own Claude or ChatGPT and let AI write, optimize, sell and publish for you.