Novamira's docs say AI abilities for WordPress should be 'never on production'

Novamira works at the PHP level ^[1]. The review says that makes anything that runs in WordPress reachable, with no list of supported plugins to wait for ^[8]. The reviewer counts that as a strength, though the same reach is also the attack surface.

The plugin ships controls, and each one narrows something. Default-off ^[6] and domain binding ^[7] decide whether abilities are enabled at all. Domain binding protects clones: a staging copy cut from production starts with abilities switched off, but the production site where they were activated keeps them on ^[7]. Newer releases add an Abilities Hub that lists every Abilities API ability on the site with its own toggle, including abilities from other plugins ^[10]. OAuth sign-in lets a user approve a client and revoke it later ^[12].

None of those checks what an approved agent does once connected. The administrator requirement answers who is asking ^[2]. In our view it does not bound the request, because Execute PHP bypasses the file restrictions ^[3].

Crash handling has a similar limit. Persistent PHP is stored in wp-content/novamira-sandbox/; when code there hits a fatal error, a shutdown handler traps it and the sandbox drops into safe mode on the next request ^[9]. We read that as covering fatal errors only. Code that runs cleanly and does the wrong thing never reaches the handler.

The review says Novamira is explicit that it is built for development and staging sites, and that "the only thing between your agent and a production site is your own attention" ^[5]. It also cites the docs saying AI abilities should be "never on production" ^[4]. Its guidance is to pick Novamira as one developer on a local or staging site with backups, and to look at a scoped server where several people or unattended agents need different levels of access ^[13]. We think that placement is right for a single developer with backups, where a bad run costs a restore.

This is one review, and we have its account of the docs. Its hands-on measurements come from 1.12.5 on 25 September 2026, and the version reviewed is 1.12.8, released 7 October ^[11], so the measured build is 12 days older than the reviewed one ^[14]. The reviewer also ran Novamira beside another MCP server and wrote that Novamira's design linter "beat ours in a like-for-like test" ^[15]. The author is on the other side of that comparison.