No validation before publishing
Malformed slug, missing meta, no featured image, incorrect structure. Your AI publishes anyway. Google indexes the error before you have a chance to catch it.
Connecting your AI assistant to WordPress via MCP takes a few minutes. Controlling what it does after is another story.
MCP (Model Context Protocol) is an open standard, introduced by Anthropic in November 2024,
that lets an AI assistant use the tools of another system. On WordPress,
an MCP server lets ChatGPT, Claude, Gemini or any compatible assistant
read your content, create drafts, edit pages and manage media.
There are three ways to set one up.
Published by WordPress.org, the MCP Adapter plugin turns the abilities declared through the Abilities API (WordPress 6.9 and later) into MCP tools. Exposure is opt-in: your AI only sees the abilities that WordPress or a plugin makes public.
Plugins that expose posts, pages and media to your AI, each with its own scope. Most then let the AI act directly on the site.
A hosted MCP server, connected to your site by a lightweight plugin (WordPress 6.0 and later). From the Solo plan, every action goes through validation rules, is logged and can be undone in one click. Any change to published content waits for your approval, unless automatic mode is on. Drafts remain freely editable.
In all three cases, your AI gets access to WordPress. The problem isn't the connection anymore. It's what happens after.
An MCP plugin gives your AI the keys to the site. It doesn't give it discipline.
Malformed slug, missing meta, no featured image, incorrect structure. Your AI publishes anyway. Google indexes the error before you have a chance to catch it.
No connector enforces your tone, structure or internal linking rules. Each publication follows the instructions of the moment, not those of your site.
Your AI edits content. Nothing tracks what changed, on which post, or when. You don't know what happened if something breaks.
Each site is connected separately. No central view, no shared instructions, no grouped alerts.
wp2ai sits between your AI assistant and WordPress. Your AI no longer talks directly to WordPress. It goes through wp2ai, which applies your editorial rules before each action, from the Solo plan.
Learn more about the architecture →
Slug, SEO title, meta description, featured image, content structure, semantic duplicates. Before every action, wp2ai analyzes what it will do and runs the rules of your plan: 12 on Solo, 30 on Pro and Agency. On published content, unless automatic mode is on, you see what changes and what blocks, then approve or reject.
Tone, target length, expected structure, linking rules. Global instructions apply across all your sites. Per-site instructions extend or override them. Configured once from the Solo plan, active at every session.
From the Solo plan, each edit is recorded: which content, what time. A WordPress revision is created before every change, so you always know exactly what existed before and can roll back if needed.
From the Pro plan, switch between sites from the same AI conversation, without changing context: up to 3 sites on Pro, 20 on Agency. Health status, alerts and internal linking for each site from one place. Editorial instructions and protection rules are independent per site.
Other plugins connect your AI to WordPress. wp2ai gives it 42 tools to actually work with: publish, audit, edit block by block, manage multiple sites. Each tool includes revision control. Validation rules and a full action log are added from the Solo plan.
Every action creates a WordPress revision. From the Solo plan, one-click rollback, 90-day action history and full audit trail.
Read, rewrite and patch Gutenberg blocks on existing content. Paragraph, heading, list. Targeted and precise.
Quality scoring, broken links, orphan posts, content freshness, internal linking suggestions. Full pipeline on every sync.
Read and write posts, update meta fields, manage categories, tags and custom taxonomies from your AI conversation.
Upload images from a URL or directly from your AI chat. Set featured images, update alt text, delete attachments.
From the Solo plan, editorial instructions persist across every session, with one-click rollback of any action and a full audit trail across all sites.
Checks before publishing. A revision before every edit. A log of every action.
wp2ai works with your editor and builds on your SEO plugin instead of replacing it. For editors, the level of control depends on the builder.
Editors and builders
Replace, insert, delete, move blocks. Each block is targeted individually. wp2ai modifies exactly what needs to change, without touching the rest.
Update existing widget or element text and delete elements. Insert and move are not supported due to each builder's proprietary structure.
Replace, insert, delete each paragraph individually. Or rewrite the entire article in a single operation. Ideal for deep updates of existing content.
SEO plugins
wp2ai reads the SEO title, meta description, canonical URL and robots directives of each piece of content, as your plugin displays them on the page, templates and separators included. From the Pro plan, it checks them before publication and flags what is missing or too long. Your SEO plugin stays in place, wp2ai builds on it.
wp2ai doesn't remove your AI's capabilities. It frames them according to what you decide.
Your AI's actions are applied directly to drafts. Request a pre-publish simulation: wp2ai checks the rules of your plan, 12 on Solo, 30 on Pro and Agency, and tells you exactly what blocks. Verify safely before deciding to publish.
From the Solo plan, each pending action shows a detailed analysis of what it will do: which blocks are affected, what changes, and why. You approve with full context, not blindly.
Made a mistake after approving? wp2ai restores the previous state in one click. A WordPress revision is created before every action. Rollback is instant, no manual correction needed.
WordPress MCP means connecting a WordPress site to an AI assistant through the Model Context Protocol, an open standard. Once the site is connected, ChatGPT, Claude or Gemini can read, create and edit content from the conversation.
Yes. WordPress.org publishes the MCP Adapter plugin, which exposes the abilities declared through the Abilities API as MCP tools. It requires WordPress 6.9. wp2ai does not depend on it: it works from WordPress 6.0 and adds validation, editorial rules and action history.
An MCP plugin connects your AI assistant to WordPress. wp2ai is a WordPress MCP server that protects your sites from AI mistakes: it adds a layer of validation, editorial memory and traceability between your AI and your sites. The logic runs on wp2ai servers, not inside WordPress.
Yes. wp2ai implements the standard MCP protocol and works with all compatible clients: ChatGPT, Claude, Gemini and any tool that supports the MCP protocol. You keep using the AI you already have.
From the Solo plan, every modification is submitted for your approval before being applied, unless you turn on automatic mode for that site. You see the analysis of what the action will do, then approve or reject. A WordPress revision is created before each change.
Yes. wp2ai creates a WordPress revision before every action it applies. If you approved a change and the result is not what you expected, you can roll it back in one click from the app. No manual correction needed, no risk of losing content.
Yes. Gutenberg and Classic Editor get full operation support. Elementor (including the Atomic Editor) and Bricks Builder support replace and delete. Insert and move operations are not available on these builders due to their proprietary structure.
No. wp2ai logic runs on our servers, not inside WordPress. The plugin installed on your site is a lightweight connector: no processing, no external calls on page load, no impact on performance.
Two minutes to install the plugin. Your AI is up and running immediately.
14-day Pro trial · No credit card · No commitment