Antigravity is Google’s agent-first development environment, and Antigravity CLI is its terminal front end, the successor to Gemini CLI. Both can work on a WordPress site through Novamira. This guide covers the routes that fit them, the setup step by step, what changed for Gemini CLI users, and the errors that come up most often.
Can Antigravity work on a WordPress site?
Yes. Connected through the Novamira CLI or an MCP configuration, Antigravity’s agent can read and write posts and pages, build Elementor and Bricks layouts, manage plugins, query the database and run PHP on the site, one visible tool call at a time. The connection is direct between your machine and your site, and Antigravity and Antigravity CLI are among the clients the Novamira > Configuration page provides specific instructions for.
Which connection method should you choose?
| Route | Setup | Best for |
|---|---|---|
| Novamira CLI | One install, one login per site | Antigravity CLI in the terminal; the simplest route |
| MCP via the mcp-remote bridge | One config block | A standard MCP setup, local sites included |
| MCP with an Application Password | Generate a credential, paste a config | Environments where the browser sign-in is impractical |
The Novamira CLI is the route built for terminal agents: one install, a guided connection per site, and automatic reconnection when a grant expires. The MCP route goes through the mcp-remote bridge, which runs the browser sign-in on the client’s behalf. The Application Password variant is the manual fallback, with the config generated for you on the site’s Novamira > Configuration page.
What do you need before you start?
- A WordPress site on HTTPS with the Novamira plugin active, free from the download page.
- An administrator account on the site.
- Antigravity, or Antigravity CLI in the terminal.
How to set up Antigravity CLI with the Novamira CLI
Install the CLI (requires Novamira 1.11.0 or later on the site):
# macOS / Linux
curl -fsSL raw.githubusercontent.com/use-novamira/novamira-cli/main/install.sh | sh
# Windows (PowerShell)
irm raw.githubusercontent.com/use-novamira/novamira-cli/main/install.ps1 | iexThe installer asks which agent you use and wires it up. Connect a site by giving the CLI its URL and approving the sign-in from your browser; over SSH or in a container the CLI shows a device code instead, which you approve from any device where you are signed in to the site. From then on, describe the task and the agent calls the site’s abilities through the CLI.
How to add a WordPress MCP server to Antigravity
Both Antigravity and Antigravity CLI connect through the mcp-remote bridge, with this shape of configuration:
{
"mcpServers": {
"novamira-your-site": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://your-site.com/wp-json/mcp/novamira-oauth"]
}
}
}The Novamira > Configuration page generates the exact snippet and the config file location for your client, with your real site URL filled in. Restart the session, approve the sign-in from your WordPress login when the browser opens, and verify that the Novamira tools appear in the tool list. Authorizations live under Novamira > Manage Connections, where revoking takes effect immediately.
What about Gemini CLI?
Antigravity CLI is the successor to Gemini CLI. If you still run Gemini CLI in an enterprise setup, the same mcp-remote configuration applies unchanged.
Watch it in action
This walkthrough from the Novamira channel connects Google’s agents to a WordPress site in about two minutes (recorded when Antigravity CLI was still Gemini CLI; the flow is the same):
A workflow that holds up
Build where mistakes are cheap, review on the rendered site, then deploy through your own process. Novamira is recommended for staging environments with backups, and Read Mode in Novamira Pro covers read-only inspection on live sites. The Claude Code guide walks through this in more detail.
Common errors and how to fix them
The bridge fails to start. The mcp-remote route runs on npx, so Node.js has to be installed. Without Node.js, use the direct HTTP configuration with an Application Password, generated on the Novamira > Configuration page.
The sign-in never completes. OAuth requires HTTPS, and some hosts filter traffic from cloud AI providers; the docs cover what to do when your host or a firewall blocks the connection.
The CLI route fails on an older stack. The Novamira CLI requires WordPress 6.9 or later and Novamira 1.11.0 or later on the site.
A tool call is refused. Check which features are enabled under Novamira > Features, and whether Read Mode is active on that site: with Read Mode on, everything that changes content, files and settings is not offered, and refused if something calls it anyway.
Next steps
Connect a staging copy and give the agent a first real task: an audit of the installed plugins, or a landing page in your builder. The tools page lists every ability it can call, and the connection docs cover every client and route in one place.