Tools · researched 15 Nov 2026
Novamira: letting Claude work inside WordPress
Novamira is a free, open-source plugin that turns a WordPress site into an MCP server, so Claude can read and change the site through tools rather than copy and paste.
Core abilities · from novamira.ai
Extra abilities seen on FAIM's install [T]
- Yoast SEO: read and update a post's SEO data, read SEO and readability scores
- Admin access links for browser automation
- Gutenberg block reading and a queued editor finaliser
- Stored skills (get, write, edit, delete)
- Design library with a pre-flight check that flags em dashes and off-palette colours
- Built-in skills: site integrity check, PHP compatibility check, design, custom theme build, Gutenberg editing
Why it helps SEO work
- Update Yoast titles, descriptions and focus keywords post by post, with the old values saved for rollback.
- Add schema or a small feature as one sandbox file; disable or delete the file to revert.
- Query the database for word counts, link counts and real publish dates across every post.
- Run the site integrity check before taking over a site.
Setup, in outline
- Take a full backup (files and database).
- Download Novamira from novamira.ai and activate it (WordPress 6.9 or later, for the Abilities API).
- Turn on AI Abilities in its settings, then open Novamira, Configuration to connect your Claude client.
- Ask Claude to list abilities first, and to change nothing until you approve a written plan.
Known limits on our host
- It cannot write server rules (.htaccess) or DNS here, so 301 rules and Search Console verification need the hosting account holder.
- It does not edit WPBakery layouts through its Gutenberg tools.
- Never let an agent update, deactivate or delete Novamira itself, or its connected user: that cuts the connection.
A competing vendor's review describes Novamira's single permission gate as a trade-off compared with per-call scopes. Treat that as a competitor's view, disclosed by its author.
BreakdownStep by step
- Understand what it is
Novamira connects Claude to a WordPress site so it can read settings, run checks and make changes through code files you can switch off.
- Use a sandbox folder
Custom code lives in one folder, one file per feature. Deleting or disabling a file reverts that feature.
- Back up before every change
And never save a backup inside that folder with a .php ending; every .php file there is loaded.
- Ask before changing a live site
Read-only checks first. Changes only after you have read the report and approved.
Worked example
A lesson we paid for on 18 Nov 2026
We saved a backup of a feature file with a .php name inside the sandbox. WordPress loaded both copies, the same class was declared twice, and the crash guard switched off every custom feature for about two minutes. Backups now end in .php.txt, and the four-day health check looks for a crash marker first.
TipsWhat works in practice
AvoidCommon mistakes
- Editing theme core files instead of using a sandbox file.
- Saving backups where they will run as code.
- Letting an agent make bulk changes without a rollback path.
Quest · Operator badge
Safe hands
Where should a backup of a sandbox PHP file go?
Why: Every .php file in the sandbox is loaded. A .php.txt backup is kept safely without running.
© 2026 FAIM Global · FAIM Digital W.L.L · Manama, Kingdom of Bahrain · info@faimglobal.com