Novamira Model Context Protocol Server Review: Capabilities and Security Guardrails
Novamira bridges WordPress sites with coding agents like Claude Code, Cursor, and Codex over the Model Context Protocol. While it unlocks deep WP-CLI, PHP, and Gutenberg manipulations, its administrative privileges demand staging-only deployment.
Why it matters
You can safely automate WordPress workflows from your IDE agent if you isolate permissions to staging environments and keep human verification active.
TL;DR
- 01Never connect Novamira MCP directly to production sites; enforce strict staging and local environments.
- 02Always create snapshots or database backups before initiating agent write sessions.
- 03Ensure agents call wp_slash() on raw JSON payloads to prevent Elementor tree corruption.
Key facts
- Plugin Version
- 1.12.8 (Reviewed 1.12.5)
- License
- AGPL-3.0 (Core)
- Pro Tier Pricing
- €49/year (3 sites), €149/year (1,000 sites), €299 lifetime
- Minimum Requirements
- WordPress 6.9, PHP 8.0, Node.js 18+ for remote proxy
Direct Agent Control Over WordPress
Novamira exposes WordPress internals via the Model Context Protocol (MCP), enabling agents in Claude Code, Cursor, and Codex to execute arbitrary PHP, trigger WP-CLI commands, run database queries, and manipulate Gutenberg block markup. The core plugin is AGPL-3.0 licensed, requiring WordPress 6.9+ and PHP 8.0+. Remote agent connections leverage HTTPS and the @automattic/mcp-wordpress-remote proxy over Node.js 18+.
The Administrator Security Trade-Off
Novamira's security guarantees are explicit: every connected agent operates as a full site administrator. While persistent PHP code is routed to wp-content/novamira-sandbox/ with fatal error shutdown handlers, the Execute PHP ability bypasses local file restrictions. Novamira does not create automated backups or provide rollback mechanisms. Running these abilities against live production databases risks irrecoverable corruption.
Gutenberg Serialization vs Page Builders
In testing, native Gutenberg editing achieved high schema fidelity by queuing modifications through real editor sessions, requiring an open wp-admin browser tab. When interacting with page builders like Elementor, update_post_meta() strips a layer of backslashes; failing to invoke wp_slash() on the JSON payload corrupts the page tree immediately.
Try it in 2 minutes
{
"mcpServers": {
"wordpress-staging": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote", "--url", "https://staging.example.local"]
}
}
}json
✓ When to use
- Rapid scaffolding and prototyping of custom themes or plugins on local Docker setups.
- Automating batch content migrations and layout generation on staging sites with full backups.
- Debugging PHP stack traces and inspecting WordPress hooks directly from your agent IDE.
✕ When NOT to use
- On production WordPress instances where untracked database mutations risk outages.
- In multi-developer teams requiring granular, role-based read-only agent access.
- For unattended scheduled background agents that cannot rely on an active wp-admin tab.
What to do today
- Clone your production WordPress database to a sandboxed staging domain before enabling AI abilities.
- Audit wp-content/novamira-sandbox/ for persistent scripts generated during test sessions.
- Configure Model Context Protocol client timeouts to accommodate multi-step Gutenberg serialization.