"My agent already has full access through SSH."
SSH gives your AI agent a shell on the server. It works, but every request carries connection overhead and every response comes back as plain text the agent has to parse. Novamira runs inside the WordPress process and speaks MCP natively. Same access, less friction.
What changes for the agent.
| Novamira | SSH | |
|---|---|---|
| Connection | HTTPS or localhost ★ | SSH key/password |
| Setup | Application Password, nothing to download | SSH access + site on server |
| PHP execution | Direct call in WordPress process ★ | Shell commands |
| Response format | Structured JSON via MCP ★ | Plain text via stdout |
| File editing | Find-and-replace | Full file rewrite |
| Execution time* | ~0.36ms per call ★ | ~1.5ms per call |
| Response tokens* | ~50 per call ★ | ~150 per call |
| Site context | Provides site context on connect ★ | Agent discovers by trial |
| Crash recovery | Sandbox with auto-recovery ★ | None |
| Built for | AI agents via MCP | Humans and shell scripts |
*Based on a single community benchmark. Results may vary.
SSH is essential for server admin, deploy pipelines, and system-level ops. Novamira is specifically for AI agents working inside WordPress. It gives them a native interface to the PHP runtime instead of routing everything through a shell. Same goal, shorter path.
This page reflects our perspective as the team behind Novamira. If something looks inaccurate, let us know.
Your WordPress. Your AI.
Nothing in between.
Free and open source. Built for WordPress 6.9+.