What if you could tell Claude, “Draft a 500-word post about the summer sale and save it as a draft on the site,” and it simply happened? No copying from a chat window, no pasting into the editor. The post shows up in your WordPress dashboard, ready for review.
That is exactly what MCP makes possible. MCP stands for Model Context Protocol, an open standard that lets AI assistants like Claude, ChatGPT, or Cursor talk directly to the systems where your data lives. Your WordPress site is one of those systems.
This guide walks through what MCP is in plain words, what connecting an assistant to your site actually enables, and how to set everything up with a free plugin. It also spends real time on safety, because giving an AI write access to a production website is not something to do casually.
Let’s start with the basics. 👇
The short version: Easy MCP AI is free on WordPress.org, connects your AI assistant straight to your site with no middleman relay, and is secure by design: read-only scopes, capability checks on every call, and an Audit log (on by default) that records every MCP tool call.
What is MCP, in plain words?
Model Context Protocol is an open standard that Anthropic open-sourced on November 25, 2024, built “for connecting AI assistants to the systems where data lives.” It was created at Anthropic by David Soria Parra and Justin Spahr-Summers, and it has since been adopted by OpenAI and Google, with support in ChatGPT and Gemini. That last part matters: one setup works across AI clients, instead of a separate integration for every assistant.
Think of MCP as a common language between two sides. On one side, your site runs a small MCP server that exposes WordPress actions as typed “tools”: create a post, moderate a comment, read an SEO title. Typed simply means each tool has a defined name, a description and a schema for its inputs, so the assistant knows exactly what it can ask for. On the other side, an AI client (Claude, ChatGPT, Cursor and others) calls those tools over the protocol when you ask it to do something.
The result: the assistant stops being a clever text box and becomes something that can actually read from and act on your site, within limits you choose.
What can an AI assistant actually do on your site?
Quite a lot, it turns out. Based on what current WordPress MCP servers expose, a connected assistant can:
- ✍️ Draft, schedule, and publish posts straight from chat. A prompt like “Write a 500-word blog post about X and save it as a draft” produces a real draft in wp-admin.
- 💬 Moderate comments: approve, hold, mark as spam, or delete.
- 🖼️ Upload media and save alt text that the AI client writes (only a client that can open the image can describe it).
- 🔍 Edit SEO titles and meta descriptions across six major SEO plugins (Yoast, Rank Math, AIOSEO, SEOPress, Slim SEO, and The SEO Framework) once you switch on that plugin’s group under Easy MCP AI → Tools → Abilities.
- 📊 Answer questions from your data, like “What keywords does my homepage rank for?” by querying Google Search Console and GA4 (once you connect those accounts).
- 🛒 Manage WooCommerce products and orders once you switch on that group under Easy MCP AI → Tools → Abilities. Menu editing works from the start, while tools that create, change or delete user accounts, such as creating users, are off by default on a fresh install.
Every MCP tool call behind those tasks lands in the Audit log, which is on by default, so there is a record of what the AI did and when. More on that in the safety section, because it deserves its own spotlight.
One clarification before moving on: MCP is about giving an outside assistant access to your site. If what you actually want is AI features inside wp-admin (content generators, chatbots for visitors, AI image tools), that is a different category, covered in this roundup of ChatGPT plugins for WordPress.
Two routes in: the official adapter or a plugin
This guide compares two practical ways to connect an AI assistant to a WordPress site: the core-standards route, or a plugin that handles the plumbing for you.
Route 1: the official MCP Adapter (the standards path). WordPress 6.9 shipped the Abilities API, a core registry where plugins declare discrete “abilities” a site can perform. The official MCP Adapter, part of the “AI Building Blocks for WordPress” initiative, exposes the abilities marked public (its default server offers three tools that discover, inspect and execute them) and serves them over HTTP at /wp-json/mcp/... (or over STDIO via wp mcp-adapter serve). Clients can point at the HTTP endpoint and sign in as a WordPress user, or, for STDIO-only clients, connect through the local @automattic/mcp-wordpress-remote proxy with WordPress Application Passwords. This is the core-aligned route, and since version 0.7.0 (October 2, 2026) it installs from WordPress.org like any plugin, but it needs WordPress 6.9 or newer and some comfort with developer tooling to connect a client.
Route 2: Easy MCP AI (Free, the plugin path). Easy MCP AI is a free WordPress.org plugin that turns a site into an MCP server in a few clicks, no command line required. It includes 280+ tools: core tools for posts, pages, media, users, comments, menus, taxonomies, revisions and settings, plugin-integration tools (47 for WooCommerce alone, plus ACF, The Events Calendar, BuddyPress and the SEO plugins named above), and data tools covering GA4, Search Console, Semrush, SE Ranking, DataForSEO and an Ahrefs Domain Rating check that uses a free Ahrefs API key. They are not all on at once: most core tools are on by default on a fresh install, plugin-integration groups are switched on under Easy MCP AI → Tools → Abilities for plugins that are active, and the data tools load once you save credentials. It requires only WordPress 6.0 and PHP 7.4, and on sites running WordPress 6.9+ it also exposes the Abilities you enable under Easy MCP AI → Tools → Abilities (a fresh install starts with the non-destructive ones already enabled, and abilities added later stay off until you enable them), so the two routes complement each other rather than compete.
Because the plugin runs on your own site, there is no middleman: no hosted relay and no Easy MCP AI account, and tool results go only to the AI client that asked for them (which processes them with its own model). The OAuth consent screen runs on your own site, and the tokens and logs live in your WordPress admin.
Here is the short version of how the two routes compare:
| Official MCP Adapter | Easy MCP AI | |
|---|---|---|
| Type | Free WordPress.org plugin (since 0.7.0), part of the AI Building Blocks initiative | Free WordPress.org plugin |
| Requires | WordPress 6.9+, developer tooling | WordPress 6.0+, PHP 7.4+ |
| Auth | WordPress user login (Application Passwords), directly or through a local proxy | Built-in OAuth server or bearer tokens |
| Best for | Developers who want the core-aligned path | Site owners who want a click-based setup |
The walkthrough below uses Easy MCP AI, since it is the more approachable of the two for most site owners.
Step 1: Install Easy MCP AI
In your WordPress dashboard, go to Plugins → Add Plugin, search for “Easy MCP AI,” then click Install Now and Activate. It is a standard plugin install: no account to create, no external service to sign up for.
Worth knowing at this point: nothing phones home on a default install. The external data connections (GA4, Search Console, Semrush, and similar) are opt-in and stay inactive until you save credentials for them yourself as an admin.
Step 2: Create a token with the least power needed
Access to your site is controlled through tokens, and each token gets its own permissions. Under Easy MCP AI → Connections → API tokens, click Create token, pick the WordPress user it acts as, and choose an Access level (Full access, Read-only or Custom).
The smart starting point is a read-only token. With read access alone, the assistant can inventory your content, answer questions about your posts, and pull reports, all without being able to change a single character. You can always create a second, more powerful token later once the setup has earned your trust.
A few reassuring details about what happens under the hood: tokens are stored SHA-256 hashed, every tool call passes WordPress capability checks (so a token can never do more than the user role behind it), each token has its own rate limit (60 requests per minute by default), and IP whitelisting is available if you want to lock access down further.
💡 PRO TIP: Start with a read-only token and live with it for a week. You will learn what the assistant is useful for before you hand it the keys to publish anything.
Step 3: Connect Claude Desktop with OAuth
Here is where the setup gets pleasantly boring. The plugin runs a built-in OAuth 2.1 authorization server (with PKCE and refresh-token rotation, for the security-minded), and it supports dynamic client registration under RFC 7591. In practice, the connect card on the Easy MCP AI → Dashboard walks you through the whole connection (Choose a client, Add this site, Confirm it works): Claude.ai and Cursor connect with one click, and Claude Desktop takes a pasted URL. You then approve the request on your own site’s OAuth screen, where you can pick Read-only, Full access or Custom, and the token exchange happens on its own.
For clients that do not speak OAuth, the bearer token from Step 2 works as the credential instead. Either way, the assistant only ever sees the permissions you granted to that specific connection.
Once connected, try something small and harmless first: “List my five most recent posts and their categories.” If the answer comes back correct, the pipeline works. 🎉
Want this on your own site? Get Easy MCP AI free on WordPress.org and follow Step 1 above. Then run the same test.
Safety first: write access is real power 🛡️
This section is not a formality, so it gets said plainly: an AI assistant with write access to a production site holds real power. It can create, edit, and delete content at machine speed, which means mistakes scale just as fast as productivity. Treat the permission decisions below the way you would treat giving a new hire admin access on day one.
The good news is that the tooling gives you serious guardrails. Use all of them:
- Read-only first. Per-token permissions let you start with an assistant that can look but not touch.
- Capability checks on every call. Each tool call is validated against WordPress user capabilities, so tokens cannot exceed the role behind them.
- Rate limits. Per-token throttling (60 requests per minute by default) keeps a runaway loop from hammering the site.
- Audit log. Every MCP tool call is recorded while the log is on (the default), so “what changed and when” is a lookup, not a mystery.
- Change history. Before/after snapshots of changes made through MCP, kept for 30 days by default. It is on by default on new installs, so check its switch under Easy MCP AI → Settings → Logging & history before your first write session.
- Force draft on create. An off-by-default setting (Easy MCP AI → Settings → Access & safety) that saves new posts, pages and other supported items the AI creates, such as WooCommerce products, as drafts. It does not stop update tools from publishing existing content, and it does not apply to Abilities.
- Backups. Before enabling any write access, confirm you have recent, restorable backups of the whole site. This is the seatbelt you hope to never need.
⚡ PRO TIP: Confirm Change history is on and switch on Force draft on create before your first write session. Drafts are easy to review; published mistakes are not.
What MCP cannot do
The hype around this stuff is loud, so here are the limits:
- 🧠 It cannot judge quality. The assistant can draft a post, but whether that post is accurate, on-brand, and worth publishing is still a human decision. It will not replace your editor, and treating it as if it does is how thin content gets published.
- 🔧 It can only use the tools it is given. If no tool exposes an action, the assistant cannot perform it, no matter how nicely you ask. MCP expands what an AI can reach, not what it can invent.
- 🔌 It does not come with your data attached. GA4, Search Console, Semrush, and similar connections are opt-in and need credentials you save as an admin. Nothing connects itself.
- 📈 It is not a strategy. The assistant can tell you which keywords your homepage ranks for. Deciding what to do about it is still your job.
- 🧩 The standards route has a floor. If you want the official adapter path, your site needs to run WordPress 6.9 or newer.
Wrapping up
MCP sounds like plumbing, and it is, but it is the useful kind: a common language that lets the AI assistant you already use read from and act on your WordPress site. The practical takeaways:
- MCP is an open standard from Anthropic, now adopted across the major AI clients, so one setup travels with you.
- A connected assistant can draft posts, moderate comments, edit SEO meta, and answer questions from your Search Console and analytics data.
- Setup is three steps: install the plugin, start read-only (a Read-only token, or pick Read-only when you approve the OAuth request), and connect your client from the Dashboard’s connect card.
- The safety model is the feature: per-token permissions, rate limits, audit logs, force draft, and backups before anything else.
Start read-only, see where the assistant actually saves you time, and widen permissions only when the trust is earned. Your future self, the one reviewing a clean audit log instead of untangling a mess, will be grateful. 👍
Ready to connect your site? The button below takes you to the free plugin on WordPress.org, and the full feature list plus per-client setup guides live at easymcpai.com.
Yes. The plugin is free on WordPress.org, including the WooCommerce and SEO-plugin integrations. Optional third-party data providers (Semrush, SE Ranking, DataForSEO) charge for their own accounts, and your AI assistant may have its own subscription, but the connection itself costs nothing.
The connection is built around least privilege: you approve exactly which tools each client may use, read-only is a first-class option, every call passes a WordPress capability check, the Audit log records every MCP tool call (on by default), and Change history keeps before/after snapshots of changes made through MCP (on by default on new installs). Start read-only and widen deliberately.
Not through a relay or an Easy MCP AI account. Your assistant talks to your WordPress site directly: the OAuth consent screen runs on your own site, tokens are stored in your own admin, and tool results go only to the AI client that requested them, which processes them with its own model provider. If you connect analytics or SEO providers, the plugin sends them your credentials and query parameters.
Claude, ChatGPT, Cursor, GitHub Copilot in VS Code, OpenAI Codex CLI, Google Antigravity and other documented clients, plus any MCP client that supports the Streamable HTTP transport. Setup depends on the client: the Dashboard’s connect card offers one click, a URL to paste, a command or a config, followed by OAuth approval or an API token.
Have you connected an AI assistant to your WordPress site yet? What would you trust it with first? Let us know in the comments section below!
FREE GUIDE
4 Essential Steps to Speed Up Your WordPress Website
Follow the simple steps in our 4-part mini series and reduce your loading times by 50-80%. 🚀
