Most WordPress MCP connectors give Claude a keyhole view of your site — posts, pages, maybe taxonomies, whatever the REST API happens to expose. Novamira is the first one I have used that gives it the same runtime access PHP code has, and after years of building and rescuing WordPress sites for clients, that difference is the whole story. When Claude creates an Elementor page through Novamira, it is not POSTing to /wp-json/wp/v2/pages and hoping; it is calling WordPress functions the same way Elementor's own editor does when you click Save.
The plugin is free, open source, and comes from the team behind Dynamic Content for Elementor. Here is the setup that actually works, the two traps that cost me real time, and the one prompt rule that decides whether you get editable layouts or HTML soup.
Why depth of access matters
Because Novamira runs inside WordPress as a plugin, Claude can read the existing site before it acts: which post types exist, which page builder is active, what Elementor templates already live in the library. Ask it to "add a project page matching my existing project pages" and it inspects a real page first, identifies the Elementor structure, and builds the new one in the same pattern. With REST-only connectors you would be pasting CSS into the chat and describing your design out loud.
That depth cuts both ways. Deep write access to a CMS is exactly why the Novamira team is explicit that this belongs on development and staging environments, not production. Treat it the way I treat any agent with database access on client work: staging copy first, backup before every session, manual review before anything ships. If that discipline sounds like overhead, this tool is not for you yet.
The install, with the trip-wires marked
The docs claim a two-minute install. Budget fifteen minutes the first time.
- Download the plugin ZIP from novamira.ai and install it via
Plugins → Add New → Upload Plugin, then activate. - Open the Novamira tab in the admin sidebar. One setting worth changing: Novamira ships with an "Atomic editor" toggle for Elementor's newest widget structure. In my testing, deactivating Atomic and enabling standard containers produced fewer malformed layouts — containers are the battle-tested Elementor primitive, and Claude generates them more reliably.
- Generate an Application Password under
Users → Profile. WordPress shows a 24-character password in groups of four, separated by spaces. Copy the entire string including the spaces — they are part of the password. It is shown exactly once. - Download the JSON config file from the Novamira tab. It is platform-specific because Claude Desktop expects different file paths on Windows and Mac. Pick the right one.
- Wire it into Claude Desktop via Settings → Developer → Edit Config, which opens
claude_desktop_config.json.
Here is the trap that ate an hour of my Saturday: use Save, not Save As. When you paste the Novamira block into the config, some editors default to Save As for unrecognized file types and quietly write the new config somewhere Claude Desktop never reads. Claude keeps loading the old, empty config, and you keep wondering why the connector will not appear. And if you already have MCP servers configured, merge the mcpServers block into the existing one instead of replacing the file — the same additive-config rule I follow in my working MCP setup for Claude Code.
- Fully quit and relaunch Claude Desktop. MCP servers only load at startup — closing the window is not quitting. Cmd+Q on Mac, system tray exit on Windows, then reopen and check the connector indicator in a new chat.
If the connector still will not show: wrong config location (the Save As trap), password pasted without its spaces, an incomplete restart, or a site on plain http:// that the Mac client refuses to trust. Use HTTPS even on staging. On macOS specifically, expect the occasional failed connector start that a second full restart fixes — a Claude Desktop quirk, not a Novamira one.
The prompt rule that decides everything
Run a trivial first command to verify the wiring: "Create a new draft page called Test Page with a heading that says Hello from Claude." Refresh wp-admin; the draft should exist. Then run the command that actually matters:
Create another draft page. Use Elementor containers and individual widgets — not raw HTML. Add a heading widget, a text widget, and a button widget linking to /contact.
The bolded clause is the single most important lesson in this whole workflow: Claude defaults to dumping everything into one raw HTML widget unless you explicitly demand widgets. An HTML-widget page renders fine on the front end, but in the editor it is one giant code block. A client cannot edit it. A designer who knows Elementor but not code cannot tweak it. You, six months from now, will not enjoy hunting through 300 lines of markup to change a button color.
When Claude builds with real widgets, every element is a first-class Elementor object — clickable, draggable, styleable through the visual controls, safe to hand to a non-technical client. So append the instruction to every page-building prompt as boilerplate. Claude mostly remembers the preference within a session, but a fresh chat resets the default. Do not trust it to remember; instruct it every time.
Where this earns its keep: bulk operations
Pages are the demo. Bulk work is the payoff. The pattern that makes Novamira worth installing is any task that touches many posts with the same logic applied to each — the dynamic-workflow mindset I use in Claude Code, pointed at a CMS instead of a codebase. Jobs it handles well:
- Metadata cleanup — find posts with missing or auto-generated meta descriptions, write better ones from the actual content, update in place.
- Taxonomy audits — inspect categories, flag ones with under three posts, propose merges, execute the re-tagging plan after you approve it.
- Custom post types — registration, supporting fields, archive template, an Elementor template for entries, and sample content, from one paragraph of prompt.
- Page cloning with variant copy — duplicate a high-performing landing page, swap only the headline and CTA text, leave every visual element identical.
What it is not good at is design from a blank prompt. "Build me a beautiful homepage for a yoga studio" produces the same competent, generic, beige result every AI page builder produces. The AI is a fast pair of hands, not a designer. You bring the layout intent; it executes the labor — and when a build goes sideways on a live client site, the recovery discipline is the same one from my WordPress critical-error case study: backup, isolate, restore, then diagnose.
Free vs Pro
The free plugin covers the core capability — Claude reading and writing your WordPress site — and for occasional page and post work it is genuinely enough. Novamira Pro starts at €49/year and adds the things that matter at agency scale: deeper Elementor and Bricks knowledge (fewer refinement prompts per layout), persistent memory so Claude remembers your brand colors and structure between sessions, and curated understanding of stacks like ACF and JetEngine.
My honest read: hobbyists and bloggers should stay on free. If you build client sites weekly, the memory feature alone justifies Pro, because re-explaining a site's structure at the top of every chat is the tax you pay otherwise.
The verdict from client-side WordPress work
This is one of the most useful AI integrations I have added to my WordPress toolkit — and it is not magic. It excels at bulk content operations, site-structure tasks, cloning, and metadata hygiene. It is adequate at building new pages from detailed prompts. It struggles with aesthetic judgment and with anything you have not backed up.
The biggest risk is behavioral, not technical: once an AI can edit your site, you will be tempted to point it at production. Don't. Staging first, backups always, review before publish — the same rules you would apply to a junior developer with database access, doubled, because this one moves faster.
The WordPress rescue jobs I get called into usually start the same way: someone gave a tool write access to production before a staging copy existed. Novamira setups that arrive with the guardrails already in place — staging clone, backup schedule, scoped access, review gate — are part of the WordPress work on my services page.
