Connect Claude to WordPress: How to Edit WordPress with AI in 2026 (and When to Move On)

There's a wave of tools that finally let an AI assistant reach into a WordPress install and do the work — read the database, run commands, edit files — instead of just writing text you paste in. Novamira is one of the clearest examples, and it works with Claude. It's impressive. But watching a demo, it's easy to ask the wrong question. The question isn't "how do I add AI to my WordPress?" It's "should I keep investing in WordPress at all, or is this the moment to move on?" Let's look at both honestly.

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. Novamira is a WordPress plugin that runs an MCP server inside WordPress, so once you connect a client the AI has a direct line in. 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 four 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 four working approaches, and they differ enormously in what the AI is allowed to touch.

1. An MCP plugin, the deepest access

This is the "connect Claude to WordPress" 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.

2. 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.

3. 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.

4. Skip the plugin: an AI-native platform

The fourth 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.

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.

Frequently asked questions

The bottom line

Connecting Claude to WordPress is real, and Novamira does it well — over an open standard, for developers working on staging. That's a good tool for a specific job. 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.