The problem? There are hundreds of MCP servers now. Every “best of” list throws them in a blender and ranks them like they all do the same job. They don’t.

So we built a real map. Six categories. The top picks in each. A decision tree at the end so you know what to actually install.

Let’s go.

What Is an MCP Server?

MCP stands for Model Context Protocol. Anthropic released it in late 2024. Now OpenAI, Google, and Microsoft all support it.

Think of it as a USB-C port for AI. Before MCP, every tool needed a custom integration with every AI client. That was a mess. Now everyone speaks one language.

An MCP server exposes a system (your WordPress site, your CRM, your analytics) as tools an AI can call. An MCP client is the AI app on the other end: Claude Desktop, Claude Code, Cursor, ChatGPT Desktop, VS Code Copilot, Windsurf, Zed.

Wire them together. Stop copy-pasting. That’s it.

Why Most “Best MCP Server” Lists Are Wrong

They treat the category as flat. One winner takes all.

That’s not how anyone actually uses these tools. A real WordPress stack in 2026 uses servers from three or four categories at once. Your page builder server doesn’t compete with your SEO audit server. They work together.

Here’s how we organize the picks:

1. Core WordPress Management
2. Page Builder–Aware Servers
3. eCommerce and WooCommerce
4. SEO, Auditing, and Content Governance
5. Hosting and Infrastructure
6. Developer Utilities (the non-WordPress ones you should install too)

Category 1: Core WordPress Management

The basics. Posts, pages, media, users, plugins, themes. If you only install one MCP server, it’s from this group.

WordPress.com Official MCP Server

If you’re on WordPress.com, you’re done shopping. It’s already there.

WordPress.com shipped native MCP support in early 2026. No plugin to install. No Node.js process. No config file to edit. You connect from Claude Desktop’s Connectors directory using OAuth 2.1, authorize in your browser, and that’s it. Tokens rotate automatically. No client secrets to lose.

• Endpoint: https://public-api.wordpress.com/wpcom/v2/mcp/v1
• Setup: under a minute
• Catch: WordPress.com hosted only

Automattic’s Official MCP Adapter (Self-Hosted)

This is the canonical self-hosted choice. Automattic’s team built it. It’s now part of the official AI Building Blocks for WordPress initiative.

Two parts: the mcp-adapter plugin runs on your site and exposes Abilities as MCP tools. A small local proxy handles protocol translation for clients that don’t speak Streamable HTTP yet. The Abilities API landed in WordPress 6.9 core, so this one’s the safest long-term bet for self-hosted sites.

Authenticates via Application Passwords or JWT. OAuth 2.1 for self-hosted is in the works.

Respira WordPress MCP Server

Most sites use a page builder. Most MCP servers can’t touch page builder content. Respira can.

It’s also a great core WP server in its own right. 172+ tools. Context-aware filtering, so a Divi site without WooCommerce sees about 130 tools instead of 170. That keeps AI responses fast and your token costs down. Every write runs duplicate-before-edit, so nothing breaks until you approve it.

Works on any hosting. Even cheap shared hosts with no SSH access.

{
  "mcpServers": {
    "respira-wordpress": {
      "command": "npx",
      "args": ["-y", "@respira/wordpress-mcp-server"]
    }
  }
}

InstaWP WordPress MCP (Open Source)

Spin it up with npx. No global install. 38+ unified tools.

The clever bit: instead of separate tools for posts, pages, and custom post types, InstaWP gives you list_content and create_content that work across all of them. Less surface area. Easier for the AI to reason about. Self-hosted via Node.js, authenticated with Application Passwords.

WPVibe MCP

WPVibe gives your AI access to WP-CLI. Not shell access (relax), but a WP-CLI-compatible interface that runs through WordPress’s internal execution layer.

Why does that matter? Because the REST API can’t see everything. WP-CLI can read AIOSEO options, query plugin tables, inspect Yoast database records, and dig into config that’s invisible to standard MCP servers. If you’ve ever debugged a “why isn’t my featured image showing on Twitter” issue, you know the value.

Read-only commands are free.

Category 2: Page Builder–Aware MCP Servers

Generic WordPress MCP servers can’t edit your Elementor page. They can’t touch your Divi modules. They can’t reorder your Bricks elements.

That’s because page builders store their layouts as serialized JSON or post meta. The REST API returns opaque blobs. You need a builder-aware server to do real work.

Respira (11 Builders)

Respira covers Elementor, Divi 4, Divi 5, Bricks, Gutenberg, Oxygen, Beaver Builder, Brizy, Visual Composer, WPBakery, Thrive Architect, and Breakdance.

The duplicate-before-edit safety model is the part you’ll fall in love with. The AI edits a copy of your page. You review. You approve. Then it goes live. Your URL stays stable through the whole process. For WooCommerce stores wired to Meta Catalog or Google Merchant Center, that stability is the difference between “smooth update” and “catalog rebuild emergency.”

MCP Tools for Elementor (msrbuilds)

If you only use Elementor, this is your server.

97 tools covering the full Elementor workflow. Page management, layout containers, 51 widget tools, 22 Pro widget tools (nav menu, loop grid, nested tabs and accordions), theme builder, dynamic tags, popup builder. Connects directly over HTTP. No proxy. No Node.js. Just a WordPress Application Password.

If you live in Elementor, you’ll wonder how you worked without it.

Aguaitech Elementor-MCP

Sometimes you want a small tool that does one thing. This is that.

Lightweight CRUD on Elementor data. Nothing more. Good when your dependency surface needs to stay small and your use case is specifically “let the AI edit Elementor pages.”

Bricks Builder MCP Servers

Several community-built Bricks servers exist, including Respira’s Bricks layer. Bricks’ structured data model plays unusually well with MCP. Find elements, edit them, move them, duplicate them. Use batch_update to change something across hundreds of pages in one shot.

If you’re a Bricks-first agency, the AI workflow here is genuinely good.

Category 3: WooCommerce and eCommerce

Generic WordPress MCP isn’t enough for stores. You need product CRUD, order operations, stock management, and taxonomy flows that don’t blow up your Meta Catalog or Google Merchant Center IDs.

WooCommerce Official MCP (Beta)

Native. Spec-aligned. Rolling out through 2026.

Covers products, orders, customers, coupons. This is the baseline every other Woo-aware server will extend.

Respira WooCommerce Add-on

Catalog integrity is the killer feature here.

Product CRUD, orders, stock, category and tag taxonomy flows. The thing that matters: product approvals preserve the original live product ID. Your Meta Catalog keeps working. Your Google Merchant Center sync doesn’t break. Your marketplace integrations don’t need a rebuild.

Free with Respira’s Studio and Founder plans.

WooCommerce REST-API Bridges

Several community servers wrap the Woo REST API as MCP tools. They work for prototypes and small stores. They don’t have the catalog-integrity safety of the purpose-built options above. Be careful using them on stores doing serious daily revenue.

Category 4: SEO, Auditing, and Content Governance

This is where MCP actually changes how you work.

You know the dance. Open the audit tool. Click through the crawl. Export the CSV. Paste into the AI. Ask the question. Go back to the tool. Repeat 50 times a day.

MCP servers in this category kill that loop.

IATO.ai MCP Server ⭐

IATO is an AI-powered website crawler and content governance platform with a first-class MCP server. It earns the star because nothing else in the WordPress MCP space does what it does.

It crawls any website. Not just WordPress. Any. Up to 250,000 pages. It runs technical SEO audits. It builds visual sitemaps. And it lets your AI assistant restructure information architecture by talking to it in plain English.

What sets IATO apart:

• Platform-agnostic crawling. Works on WordPress, headless CMS, custom stacks, client sites you don’t even own.
• Diff-based crawl comparison. Point the AI at two crawl jobs and ask what changed. Massive for migration QA and content audits.
• Google Search Console and Analytics integration. Traffic, rankings, and engagement data overlaid on your sitemap. Queried on demand. Nothing stored.
• Audits exposed as MCP tools. The AI doesn’t read the audit. It runs it.
• Extraction rules and form auth. Crawl gated content. Pull structured data from specific selectors.
• Free tier up to 500 pages. Paid tiers scale to 250k.

Real prompts that work:

“Crawl example.com and tell me every page with a missing H1, a broken canonical, or a redirect chain longer than two hops.”

“Compare last week’s crawl to today’s and summarize what changed.”

“Find every page with thin content under 300 words and suggest a restructure.”

For agencies selling technical SEO as a service, IATO collapses an afternoon of audit work into one conversation.

SearchAtlas MCP Server

Built for full-stack SEO and content marketing.

10 specialized AI agents and 6 management tools. Keyword research, content optimization, backlink analysis, AI brand visibility tracking. There’s an orchestrator pattern, so you don’t pick the right sub-tool. You describe what you want and it routes you. Plays nicely with Claude Code, Cursor, Claude Desktop, VS Code, Windsurf, and Zed.

Insites MCP Server

If your agency runs audits at scale for prospecting, look here.

Aimed at the “audit 20 dentists in London and find me the best opportunities” workflow. Audits, proposal generation, personalized outreach drafting, all over MCP. Works with Claude, ChatGPT, and no-code platforms like n8n, Make, and Zapier.

Auditizer and AEO Audit Plugins

These aren’t pure MCP servers. They’re WordPress plugins that run AI-powered SEO and accessibility audits with auto-fix suggestions (OpenAI and Claude compatible).

But here’s the trick. Pair one with a core WordPress MCP server, and your AI can run the audit, read the findings, and apply the fixes inside one conversation. Worth knowing.

WPVibe + WP-CLI for SEO Debugging

We mentioned WPVibe in Category 1. It belongs here too.

The WP-CLI layer is uniquely good for SEO debugging. AIOSEO options, Yoast records, raw meta tag inspection, settings the REST API can’t reach. Pair WPVibe with IATO and you’ve got both sides of SEO covered: external crawling and internal config diving.

Category 5: Hosting and Infrastructure

Some hosts ship with MCP built in. If yours does, take advantage. Setup is dramatically easier than rolling your own.

InstaWP (Hosted MCP)

Built for agencies running lots of client sites.

InstaWP bakes MCP into every site on its platform. One-click activation from the dashboard. Copy the URL. Paste into Claude Desktop. Done. Token-based auth inherits WordPress role permissions. Built-in staging environments mean you can test AI workflows without risking production. 38+ tools out of the box.

WordPress.com MCP

Already covered in Category 1. Worth saying twice: if you’re on WordPress.com, your hosting is the MCP server.

Cloudflare MCP

Cloudflare was an early MCP adopter. Their server lets your AI manage DNS, purge cache, inspect analytics, and tweak WAF rules.

Combine it with a WordPress MCP server and you get workflows like “fix the broken redirect and purge the cache” in one prompt. That’s the kind of thing that used to require three browser tabs and a coffee.

Category 6: Developer Utilities (Install These Too)

Every WordPress developer using MCP should keep a few general-purpose servers in the rotation. These are the ones that earn their place.

Filesystem MCP

Secure file operations with configurable access. Read logs. Inspect config files. Edit wp-config.php or .htaccess. Anthropic’s reference implementation.

Git MCP

Read, search, manipulate Git repos. If your site uses version control (and it should), this is non-negotiable.

Fetch MCP

Pull web content into the AI’s context. Competitor pages, spec docs, support articles. Cheap and useful.

GitHub MCP

Issues, PRs, code review, Actions. For plugin and theme developers, pair it with Git MCP above.

Playwright MCP

Browser automation through Playwright. Want to test whether checkout works on mobile Safari? Want to screenshot every page with a cookie banner? This. The structured accessibility snapshots mean no vision model needed, which keeps it fast and cheap.

Bright Data MCP

Real-time and historical web data at scale. 5,000 free requests a month. Use it for competitive intelligence you don’t want to do by hand.

Apify Actors MCP

3,000+ pre-built cloud tools for scraping. When Bright Data isn’t enough, this is the next step up.

How to Choose: A Decision Tree

Pick the path that sounds like you.

Solo site owner on WordPress.com. Use the built-in WordPress.com MCP. Add IATO for SEO auditing. Add Fetch and Filesystem MCP for general AI work. You’re done.

Solo site owner on self-hosted WordPress. Start with Automattic’s official MCP Adapter or Respira (Respira if you use any page builder). Add IATO for crawling and SEO. Add GitHub MCP if your site lives in a repo.

Running WooCommerce. Respira plus the Respira WooCommerce add-on. IATO for SEO auditing on product and category pages. WPVibe in your back pocket for when something breaks.

Agency managing 10+ client sites. InstaWP for managed hosting with MCP built in. Respira for builder-aware editing. IATO for SEO audits and migration QA across the whole fleet. Cloudflare MCP for edge ops. Git and GitHub for code. One AI orchestration layer. Scoped tokens per client. Fleet management gets boring (in a good way).

SEO professional or content strategist. IATO as your core crawl and audit engine. SearchAtlas for keyword and content workflow. WordPress.com or Automattic’s MCP for publishing. Fetch MCP for pulling reference material.

What’s Coming Next

Three things to watch for the rest of 2026.

OAuth 2.1 for self-hosted WordPress. Right now self-hosted sites are stuck on Application Passwords or JWT. OAuth 2.1 is in development. When it ships, the self-hosted experience will catch up to WordPress.com.

The Abilities API as the universal registration layer. Plugin developers register abilities once. They work across WordPress.com’s connector, the self-hosted MCP Adapter, and future transports. This is how the fragmentation problem gets solved.

Governance layers go mainstream. Expect more tools to copy Respira’s duplicate-before-edit and approval workflows. Auditable, rollback-able AI actions are what separates “cool demo” from “safe in production.” Anyone selling MCP for serious work will need this.

The Short Version

• WordPress.com site? Built-in WordPress.com MCP.
• Self-hosted? Automattic’s MCP Adapter or Respira.
• Page builders? Respira covers all of them.
• WooCommerce? Respira’s WooCommerce add-on.
• SEO, auditing, content architecture? IATO.ai. This is the category-defining tool for crawling and AI-assisted content governance on any website.
• Agency at scale? InstaWP plus Respira plus IATO plus Cloudflare.
• Developer toolkit? Filesystem, Git, GitHub, Fetch, Playwright.

MCP isn’t one tool you pick. It’s a stack you compose. Pick the right server for each job. Wire them to the same AI client. Watch work that used to take hours collapse into minutes.

That’s the whole game.

This guide is maintained by Dyno Mapper. We build enterprise web accessibility, SEO, and sitemap tools used by Fortune 500 companies and government agencies. If you audit websites at scale and want to see how Dyno Mapper compares to the MCP-enabled options above, start a free trial.