Connect Claude to WordPress: How to Edit WordPress with AI in 2026 (and When to Move On)
Key takeaways
- Five ways to edit WordPress with AI today: the official MCP connection, a developer MCP plugin, the REST API, an in-admin assistant, or an AI-native platform.
- The official connection is the new default. WordPress.com connector or Jetpack, a limited user, drafts first.
- Developer plugins and the raw REST API write live. They belong on staging with backups, not pointed at a business site.
- Judge any AI agent on three things: can it read the real page, does it stage the change, can you roll it back.
- An AI plugin doesn't remove WordPress's costs, it adds one more plugin to the update treadmill.
- For content-heavy sites, a static site with the AI editor built in gives you the editing without the stack.
2026 is the year AI assistants got a proper way into WordPress. WordPress 7.0 put the Abilities API into core, WordPress.com opened MCP write tools on its paid plans in March, and developer tools like Novamira let Claude run code on a site. So you can now ask Claude to do the work instead of writing text you paste in. That raises two questions: how do you connect it, and is it worth building more on WordPress at all? Let's look at both honestly. For the wider pros and cons, see WordPress and AI: what MCP changes.
What connecting Claude to WordPress actually looks like
The bridge is the Model Context Protocol (MCP), an open standard that lets an AI client operate an external system. There are now two kinds of MCP connection for WordPress, and they differ a lot in how far the AI can reach.
The official route: WordPress.com, Jetpack and the MCP Adapter
This is the one the "WordPress now supports MCP" posts are about. The AI gets a fixed set of tools, such as "create a draft post", "update a page" or "set alt text", and works within the rights of the WordPress user it signs in as.
- WordPress.com (paid plan): open Preferences, then AI and MCP, and switch on Enable MCP access, for all sites or selected ones. Choose which read and write tools are allowed. In Claude, add WordPress.com from the connectors directory and sign in. ChatGPT works through the WordPress.com app in its settings.
- Self-hosted with Jetpack: the same tools, with a Jetpack AI or Jetpack Complete plan.
- Self-hosted with the MCP Adapter: the official plugin (WordPress 6.9 or newer) turns the abilities WordPress and your plugins register into MCP tools. On its own it exposes only a few site-info tools, so editing needs plugins that register more, or custom code. You connect with an application password or OAuth. Claude's connectors reach your site from the internet, so a local site needs a local connection through WP-CLI with Claude Code or Claude Desktop instead.
The guardrails are reasonable: new posts and pages start as drafts, the AI describes each change and asks before it applies it, and changes appear in the Activity Log. Two things to know: an edit to a published page goes live at once, and some deletions (categories, tags) are permanent. The official setup notes are on WordPress.com's MCP support page.
The developer route: Novamira and similar plugins
Novamira is a WordPress plugin that runs an MCP server inside WordPress with far wider access, so once you connect a client the AI has a direct line into the code and the database. Because it speaks MCP it isn't Claude-only (it also connects Cursor, Windsurf, Zed, Gemini CLI and VS Code with Copilot), but Claude is the headline case.
What it unlocks is real: Claude writes and runs actual PHP and WP-CLI, queries your database, and edits files in place. In Novamira's own words it's real code that "actually runs. Not suggestions. Not snippets." It's honest about the trade, too: only new PHP files are sandboxed and recoverable, while database changes, config edits and code execution run live, with no preview or rollback step. That's why its guidance is blunt: "for development and staging environments, with backups, always" and "full access, full responsibility." For a developer building on a throwaway copy, that's exactly the right tool. The trap is assuming it belongs on your live site because the demo looked easy.
How to edit WordPress with AI: the five options in 2026
"Connect Claude to WordPress" is one specific answer to a broader question people are actually asking: how do I get an AI to make the change instead of telling me how to make it? There are five working approaches, and they differ enormously in what the AI is allowed to touch.
| Approach | What the AI can do | Preview before it lands? | Safe on a live site? |
|---|---|---|---|
| 1. Official MCP connection (WordPress.com connector, Jetpack, MCP Adapter) | Draft and publish posts, update pages, manage media, terms and comments | Drafts yes; edits to published pages go live | Yes, with a limited user and drafts first |
| 2. Developer MCP plugin (Novamira and similar) | Run PHP and WP-CLI, query and write the database, edit files | No, changes apply live | No, staging with backups |
| 3. REST API + application password | Create and update posts, pages and media | Only if you publish as draft | Partly, drafts only |
| 4. In-admin AI assistant (block-editor plugins) | Draft and rewrite text inside the editor | Yes, you're in the editor | Yes, but it's writing help, not site editing |
| 5. AI-native static platform | Read and edit the real page, site-wide | Yes, approve or reject each change | Yes, with one-click rollback |
1. The official MCP connection, the new default
The setup described above: WordPress.com's connector, Jetpack or the MCP Adapter. The AI works with a fixed set of content tools and the rights of its user, and asks before each change. It is strongest at content operations: drafts, metadata, alt text, categories and comments across many posts. Its limits are that it works on stored content rather than the rendered page, page builder layouts (Elementor, Divi) are often out of reach, and edits to published pages are live at once. Give it its own Author or Editor account, not an administrator.
2. A developer MCP plugin, the deepest access
This is the Novamira route described above: a Model Context Protocol server running inside WordPress, so Claude gets a direct line to PHP, WP-CLI, the database and the filesystem. It is the most capable option by a distance, and the most dangerous, because there's no staging step between the model's decision and your live database. Excellent on a throwaway copy. Not something to point at a business site.
3. The REST API with an application password
WordPress ships a REST API, and you can mint an application password under Users → Profile that lets an external agent authenticate against it. An agent with that credential can list, create and update posts, pages and media. It cannot edit theme files, run PHP or change settings, which is exactly why some people prefer it: the blast radius is content, not the site. The safe pattern is to have the agent write drafts and review them yourself in wp-admin. The limitation is that the agent is working with post content in isolation, not the rendered page, so it can't reliably reason about layout or anything the theme adds.
4. An in-admin AI assistant
Plenty of plugins now add a "write this with AI" button to the block editor. These are genuinely useful for drafting and rewriting, and they're safe because you're sitting in the editor when the text appears. But they are writing tools, not editing agents: they can't change your prices across nine service pages, update the header on every page, or fix a broken link site-wide. If that's the job you had in mind, this option won't do it.
5. Skip the plugin: an AI-native platform
The fifth route is to stop adding AI to WordPress and instead run the site on something built for it. That's what we argue for below, and it's the same conclusion the migration guides reach from a different direction, see how to migrate WordPress to a static site and the conversion tooling compared.
What an "AI agent for WordPress" can and can't do safely
Whichever route you pick, the same three questions decide whether you'll be comfortable with it in six months:
- Can it read the real page? An agent working from post content alone doesn't see what the theme, the page builder and the plugins add. It will confidently change something that then renders differently. An agent that reads the rendered page can reason about what visitors actually see.
- Does it stage the change? This is the big one. "Applies immediately" and "autonomous" are a bad pairing on a site that earns money. You want a diff you can read before it's live.
- Can you undo it in one click? If the answer is "restore last night's backup", you don't have an undo, you have a disaster recovery plan. Those are different things.
There's also a boundary worth setting regardless of tooling: don't give an agent write access to billing, user accounts, or anything that emails your customers. Content and layout are recoverable. A batch email is not.
The diesel-engine problem
Step back and the pattern is familiar. Every few years WordPress gets a new bolt-on that promises to fix the friction: a page builder, a caching plugin, a security plugin, and now an AI plugin. Each one adds capability and, quietly, more machinery to maintain. You end up with a very sophisticated version of the same aging foundation.
"Adding AI to WordPress is like trying to make the diesel engine a little bit better. You can do it, but you're still stuck with the emissions, the servicing and all the moving parts. Moving to a static site is switching to the EV: a cleaner architecture with far more upside and far less to go wrong. For most sites, that's simply the better trade." — Alex Spahn, founder of ShiftPress
The point isn't that the diesel doesn't run. It's that when you're choosing what to drive for the next decade, tuning the old engine is rarely the best use of the money. WordPress powers a huge share of the web, but for a lot of sites the reasons it was chosen (cheap, flexible, everyone knows it) are now outweighed by what it costs to keep it safe, fast and current. We made the broader case in why WordPress feels like work.
What you inherit when you bolt AI on
Adding an AI plugin doesn't replace WordPress. It sits on top of it. So you keep everything underneath, and take on a little more:
- The security surface. Core, the theme and every plugin is attack surface, and WordPress's popularity makes it the most-targeted platform on the web. A plugin that can run live PHP and write to the database is powerful, and it widens that same surface, which is precisely why Novamira insists on dev, staging and backups. More in common WordPress security flaws.
- The maintenance. You've added one more plugin to keep updated and compatible, on a stack that already asks for constant updating. Every plugin is a future breakage waiting for an update it doesn't like.
- The cost. You're still paying for hosting that can run PHP and a database, and now you stack another subscription on top (Novamira's Pro tier is €49/year). Bolt-ons add up; see what a WordPress site really costs to maintain.
- The fragility. Live PHP and a live database mean a wrong change can take the site down, and with direct, no-preview access, "undo" is a backup restore, not a click.
When WordPress still makes sense
This isn't "WordPress is dead." For genuinely dynamic applications, its database-driven nature is doing real work every second: an online shop with a cart, stock and checkout; a busy forum; a membership or course platform; a complex custom web app. There the moving parts are the product, and a developer tool like Novamira (used on staging, with backups, exactly as intended) is a reasonable way to build faster. If that's you, connecting Claude to WordPress can be a real win.
When moving on wins (which is most sites)
The mismatch is the content-heavy site: a brochure site, a local service business, a blog, a portfolio, a marketing site. It mostly presents fixed pages that change occasionally. For that job, a database, a theme and a stack of plugins rebuilding every page on every visit is a lot of machinery to secure, update and pay for, to do something a static site does faster, cheaper and more safely. And static pages, with the content right there in the HTML, are exactly what Google and AI answer engines read best, so the same move helps you get found by AI.
The catch used to be that static sites were hard to edit. That's the part AI actually solves: not by clinging to WordPress, but by making a simpler foundation effortless to change.
The cleaner model: static, with AI built in
That's the approach ShiftPress takes. It moves your existing WordPress site to fast static pages (same look, same content, same rankings), then puts an AI editor on top of that clean foundation. You type or say what you want ("update my prices", "add a section about the new service", "change the holiday hours"), and the AI reads the real page, makes the change, and shows it to you as a suggestion you accept or reject before anything goes live. See it on editing your site just by talking.
You get the thing everyone wanted from "AI + WordPress" (an assistant that reads your site and makes the edit) without the diesel underneath. No PHP runtime, no live database, no plugin stack for an agent to break, and every change staged and reversible.
| Add an AI plugin to WordPress | Move to a static, AI-native site | |
|---|---|---|
| Foundation | Legacy stack: database, theme, PHP, plugins | Fast static pages, content in the HTML |
| Security surface | Core + every plugin, now widened | Little to attack, nothing live to exploit |
| Maintenance | One more plugin on the update treadmill | No plugins, no updates to chase |
| Cost | Hosting + stacked subscriptions | One managed platform, no PHP host |
| How AI changes things | Live PHP & DB writes, no preview | A suggestion you accept or reject |
| Best for | Shops, forums, complex web apps | Content-heavy sites (most sites) |
Don't tune the diesel. Switch the engine.
ShiftPress moves your WordPress site to fast static pages that keep your look and your rankings, then lets you change anything just by talking. No plugins, no database, nothing for an agent to break. Start with a free look at your site.
Migrate my site ↗How to decide
- Running a genuinely dynamic app (shop, forum, membership, custom platform)? WordPress can still be the right tool, and a dev tool like Novamira with Claude is a strong fit on staging, with backups.
- Running a content-heavy site (brochure, local service, blog, portfolio, marketing)? You're likely maintaining far more machinery than the job needs. Moving to static removes it.
- Whatever you choose, don't wire an autonomous agent into production: direct live PHP and database access has no undo but a backup restore.
- Scan before you add anything. Know what your live WordPress already exposes. Run the free WordPress check.
- If maintenance, cost and fragility are the real problem, they don't get fixed by another plugin. See moving off WordPress without losing rankings.
More on building with AI: our guide on how to build a website with AI compares every route, from a chat AI to an AI website builder. Related: Claude vs ChatGPT for websites and building a website with ChatGPT.
Frequently asked questions
How do I edit WordPress with AI?
What is the best AI agent for WordPress?
Can Claude edit my WordPress site directly?
How do I connect Claude to WordPress.com?
Can I connect Claude to WordPress with Novamira?
Should I add AI to WordPress, or move off WordPress?
What do you inherit when you add an AI plugin to WordPress?
Does WordPress still make sense for any sites?
Novamira vs a static site: which should I choose?
The bottom line
Connecting Claude to WordPress is real. The official connection through WordPress.com, Jetpack or the MCP Adapter is the sensible default for content work, and Novamira is a strong tool for developers on staging. But for most site owners the smarter question is the bigger one: adding AI to WordPress is tuning the diesel, when the honest upgrade is a different engine entirely. For a content-heavy site, moving to fast static pages (same look, same rankings) sheds the security surface, the plugin maintenance and the stacked costs, and the AI that edits your site comes built in. That shift, from a web of documents to a web of agents, is the story we tell in the next era of the web. If you're weighing the move, start with migrating WordPress to a static site, and scan your current site first so you know exactly what you're leaving behind. If you are weighing platforms rather than plugins, we compare what their AI really does in AI and the German website builders, and step back to the general question in editing your website by chat.