Saddle vs Novamira

Last verified: August 19, 2026.

Disclosure: PlugPress makes Saddle. Novamira is a competing product. We link to the public Novamira pages used for this comparison and include areas where Novamira is the stronger fit.

Saddle vs Novamira: which WordPress MCP is right for you?

Short answer: Saddle is the better fit when you want an AI agent to work through a defined set of permissioned WordPress tools, especially on a production site. Novamira is the better fit when you want an AI agent to behave much more like a developer with PHP execution, WP-CLI, database access and filesystem control — particularly on development or staging sites.

Both products are self-hosted. Your AI client connects directly to WordPress rather than routing every MCP call through a vendor-hosted proxy. The real difference is not where they run. It is how much power they deliberately expose.

Saddle vs Novamira at a glance

Area	Saddle	Novamira
Connection model	Self-hosted MCP endpoint on your WordPress site	Self-hosted MCP endpoint on your WordPress site
Main philosophy	Named, permissioned WordPress operations	Full programmatic WordPress access for an AI developer
Fresh-install posture	Starts read-only; site owner expands access	Actions are reviewed/approved, but the available tool surface includes powerful development operations
Advertised capability count	61 things AI can do free; 108 with Pro	Novamira documents nine core abilities that provide broad programmatic access
Run arbitrary PHP	Not part of Saddle’s public tool model	Yes
WP-CLI	Not exposed as a generic command surface	Yes
Database access	Through specific tools rather than arbitrary database queries	Direct database-query capability
Filesystem access	Focused on WordPress operations, not general filesystem control	Read, write, edit, delete and explore files
Deletion safeguards	Preview plus single-use confirmation token	Agent actions can require review/approval; file changes include sandbox/recovery mechanisms
Page verification	Built pages can be re-read and scored 0–100	Novamira recommends pairing with browser MCP tools for visual inspection and iteration
Builder specialization	Saddle Pro includes builder-specific workflows, including Divi tooling	Novamira Pro advertises specializations for Divi 5, Elementor, Bricks, Beaver Builder, Breakdance, WPBakery and others
Recommended environment	Designed around controlled WordPress operations	Novamira explicitly says development and staging environments, with backups

The biggest difference: controlled operator vs AI developer

Saddle tries to make each capability understandable before you grant it. An agent gets named operations for content, media, settings, page building and other WordPress jobs. A fresh install starts read-only, and destructive operations such as deletion require an explicit second step.

Novamira deliberately goes further. Its public documentation says the AI can execute PHP with the full WordPress environment, inspect and change files, query the database and run WP-CLI commands. That gives the agent enough power to inspect an unfamiliar stack, prototype against the live WordPress runtime and build custom functionality without waiting for a dedicated integration.

That is not a flaw in Novamira. It is the product. It also explains why Novamira repeatedly positions the product for development and staging environments and tells users to keep backups.

Where Novamira is stronger

If the task is genuinely development work, Novamira has the broader surface.

PHP execution: the agent can run WordPress-aware PHP directly.
WP-CLI: it can execute commands and background longer-running jobs.
Filesystem: the agent can inspect and edit the actual plugin and theme files it needs.
Database: it can query the site’s real data while debugging or building.
Stack specializations: Novamira Pro publishes dedicated knowledge for multiple builders and plugins, including ACF and WooCommerce.

If your request is “debug this plugin conflict,” “build custom PHP for this site,” or “migrate this data with WP-CLI,” Novamira’s design is closer to the job.

Where Saddle is stronger

Saddle is intentionally less general-purpose. Instead of giving the model a programming environment and trusting it to use that environment correctly, Saddle tries to expose the operation you actually want.

That matters when the AI is working on a production site. A tool such as “update this page” has a much narrower blast radius than “execute PHP.” A tool such as “delete this page” can enforce a preview and confirmation step in a way a generic code-execution primitive cannot guarantee for every possible program the agent writes.

Saddle also has a page-verification workflow. After a page build or edit, an agent can re-read the saved state and get a score with structural, ignored-style and design findings instead of assuming that a successful write means the front end is correct.

Is Novamira unsafe?

No. “More powerful” and “unsafe” are not interchangeable claims.

Novamira documents approval-based operation, OAuth or WordPress Application Password authentication, sandboxing for newly written PHP files and recovery-oriented workflows. It is also unusually explicit about the risk: its own site says the AI can do anything PHP can do and recommends development or staging sites with backups.

The useful distinction is risk model. Novamira gives the agent developer-level primitives and asks you to supervise them. Saddle tries to reduce the number of cases where the agent needs those primitives in the first place.

Do both keep the MCP connection on your site?

Yes. This is one area where Saddle and Novamira are philosophically close. Both currently describe a direct connection from the AI client to WordPress, with no vendor-hosted MCP proxy in the middle.

If self-hosting is your deciding factor, both belong on the shortlist. The next question should be how much execution power you want available through that endpoint.

Which should you choose?

Choose Saddle if…

You want a self-hosted MCP endpoint with a deliberately constrained tool surface.
You are primarily operating content, pages, settings and structured WordPress workflows.
You want a fresh connection to start read-only.
You want destructive actions to require a separate confirmation step.
You expect the agent to work on production WordPress sites.

Choose Novamira if…

You want the AI to function as a WordPress developer, not just an operator.
You need PHP execution, WP-CLI, database queries or filesystem edits.
You are working in a development or staging environment with backups.
You want the agent to discover unfamiliar plugins by inspecting their actual code and runtime.
You want Novamira Pro’s broader builder/plugin specializations.

Our take

Novamira is one of the clearest alternatives to Saddle because it makes almost the opposite product decision. Saddle asks, “what specific WordPress operation should the agent be allowed to perform?” Novamira asks, “what would a capable WordPress developer need in order to solve this?”

For development and staging, that breadth can be a major advantage. For production operations, we prefer the narrower Saddle model.

If you want that constrained approach, see Saddle. If you need full development primitives, read Novamira’s current documentation before deciding.

Compare other WordPress MCP options

Frequently asked questions

Can Novamira execute PHP on WordPress?

Yes. Novamira publicly documents PHP execution with access to the loaded WordPress environment.

Can Novamira run WP-CLI?

Yes. Its current tools page advertises WP-CLI execution, including background jobs for longer migrations and bulk work.

Does Saddle give an AI arbitrary PHP execution?

No such generic PHP-execution capability is part of Saddle’s current public tool model. Saddle exposes named WordPress operations instead.

Is Novamira intended for production sites?

Novamira’s current documentation explicitly recommends development and staging environments and tells users to keep backups.

Are both products self-hosted?

Yes. Both currently describe the MCP connection as running directly between the AI client and your WordPress site rather than through a vendor-operated MCP proxy.

Sources

Novamira is a trademark of its respective owner. PlugPress and Saddle are not affiliated with or endorsed by Novamira. Product information changes; this page compares publicly documented features as of the verification date above.