Connect Antigravity to your own WordPress site over the Model Context Protocol. Antigravity talks to your site directly — there is no relay in between, no account to create, and your credentials never leave your machine. Setup takes about a minute once MCP Manager is installed.
Free plugin · No account · Runs on your own server · Any WordPress host
Config file
~/.gemini/config/mcp_config.json
Top-level key
mcpServers
Workspace scope
.agents/mcp_config.json
Before you start
You need AcrossAI MCP Manager installed and active on the WordPress site you want Antigravity to reach, plus an administrator account on that site. If you have not installed it yet, follow the Get Started guide first — it takes about a minute, and the MCP server ships bundled with the plugin.
You also need Node.js available on the machine running Antigravity, because the connection runs through an npx bridge. Nothing is installed permanently — npx fetches the bridge on demand.
How to connect Antigravity to WordPress
Step 1
Open Quick Connect and choose Antigravity
In wp-admin go to AcrossAI → MCP, open the server you want to expose, and start Quick Connect. Pick Antigravity from the client list. Everything below is generated for you with your real site URL and username already filled in — the snippets here are only so you know what to expect.
Step 2
Generate an Application Password
Click Generate password in the wizard. This creates a standard WordPress Application Password — not your login password — scoped to this connection and revocable at any time from your user profile.
The password is shown once, at creation. Copy it whole, including the spaces — WordPress accepts them. If you lose it, generate a new one rather than trying to recover it.
Step 3
Paste the config into ~/.gemini/config/mcp_config.json
Copy the JSON from the wizard, open ~/.gemini/config/mcp_config.json — create it, and the config directory, if they do not exist — and paste the entry under the mcpServers key. If you already have other MCP servers configured, add this one alongside them rather than replacing the file.
Watch the path. Antigravity keeps its MCP servers in ~/.gemini/config/mcp_config.json. One level up, in the same ~/.gemini directory, sits settings.json — that file belongs to Gemini CLI, which is a different program with a different structure. Editing the wrong one is the commonest reason a connection never appears. For the command-line tool, use Connect Gemini CLI to WordPress instead.
To scope the connection to one project rather than every workspace, put the same JSON in .agents/mcp_config.json at the root of that workspace. Antigravity reads it when the folder is open, which keeps a client site’s credentials out of your global config and out of your other projects.
Either file takes the same shape, with your own values in place of the placeholders:
{
"mcpServers": {
"your-site-mcp-adapter-default-server": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
"env": {
"WP_API_URL": "https://example.com/wp-json/acrossai/mcp",
"WP_API_USERNAME": "your-wp-username",
"WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
}
}
}
}Step 4
Restart Antigravity and check the tools
Antigravity reads mcp_config.json when it starts, so quit it completely and open it again — reloading the window is not reliable. Your site should appear as an MCP server, and the toolsets it exposes become available to the agent. Ask something harmless to confirm it is live — “Which plugins on this site need updating?” is a good first test.
Restart again after any change to what the server exposes in wp-admin. MCP clients receive their tool list once, at connection time, and Antigravity is no exception.
What Antigravity can do once it is connected
With Abilities Manager installed alongside it, Antigravity reaches 350+ abilities across 14 toolsets — rising past 800 once it detects the plugins you already run. Antigravity is agent-first, so it does not only answer questions about the site; it can plan a change against the live install and carry it through:
- Read and edit content — posts, pages and any custom post type with their meta and revisions, and surgically edit a page’s block tree without rewriting the page.
- Debug a broken site — read the debug log with secrets redacted, check Site Health, list recent fatal errors and un-pause what WordPress auto-disabled.
- Inspect the database — schema and table sizes, index health, bloated autoloaded options, or
EXPLAINon a slow query. - Manage plugins, themes and core — search WordPress.org, install, update, roll back, and verify files against official checksums.
- Close the loop on its own code — write a change in the editor, then read the live site’s debug log and Site Health through the same agent run to see whether it worked.
- Reach the plugins you already run — WooCommerce, Elementor, ACF, Rank Math, Yoast, WPCode and more, each registering only when that plugin is active.
Every ability runs WordPress’s own capability check for the calling user, so Antigravity can never do anything your account could not already do. See the full platform overview for the complete catalogue.
Frequently asked questions
Is connecting Antigravity to WordPress free?
Yes. AcrossAI MCP Manager and Abilities Manager are both free and GPL on WordPress.org, and there is no AcrossAI account to create. You use the Antigravity install you already have — AcrossAI never charges for AI inference, because none of it runs here.
Does my site data pass through AcrossAI servers?
No. Antigravity connects straight to your own domain and every request terminates at your /wp-json/ route. There is no relay, no gateway and no telemetry. Whatever Antigravity reads is still processed by its AI provider, so treat it as you would any other prompt.
Does it work on any WordPress host?
Yes, provided you can reach wp-admin. Shared hosting, VPS and managed WordPress all work, because everything runs inside your own install. MCP Manager needs WordPress 7.0 or later and PHP 8.1 or later; Abilities Manager needs WordPress 6.9 or later.
Can Antigravity break my site?
Every ability runs WordPress’s own capability check for the calling user, so Antigravity can never exceed what your account can already do. That matters more in an agent-first editor, where a long run may take many steps without you reading each one. Higher-risk operations refuse to run without an explicit confirmation flag, file access is confined to an allowlist you define, and any ability can be disallowed site-wide.
How do I disconnect Antigravity again?
Revoke the Application Password from your WordPress user profile, or remove the entry from ~/.gemini/config/mcp_config.json — and from any .agents/mcp_config.json you added to a workspace. Access is re-checked on every request, so revoking takes effect immediately even if the config is still on the machine.
Troubleshooting
You edited ~/.gemini/settings.json by mistake
This is the single most common failure, because the two files share a directory. Antigravity reads ~/.gemini/config/mcp_config.json. ~/.gemini/settings.json is Gemini CLI’s file, and an mcpServers block added there is invisible to Antigravity — the CLI will happily pick it up, which makes the mistake harder to spot, since the server then works in one tool and not the other. Move the entry into config/mcp_config.json, or, if the CLI is what you actually wanted, follow Connect Gemini CLI to WordPress.
A workspace config in .agents/ is ignored
The file has to be at .agents/mcp_config.json in the root of the folder Antigravity currently has open. A copy nested inside a subdirectory, or sitting in a sibling repository, is not read. If you opened a parent folder containing several projects, the workspace root is that parent, not the project you are working in. When a global config and a workspace config both define a server, check which file actually holds the entry you edited before debugging anything else.
Antigravity does not list the server at all
Quit Antigravity fully and reopen it — the config is read at startup, and reloading the window is not always enough. Check the file is valid JSON: a trailing comma or a missing brace makes the whole file be skipped silently. Confirm your entry sits under mcpServers and not at the root. If nothing else explains it, check Node.js is installed, since the bridge runs through npx; where Node comes from a version manager, Antigravity may not inherit your shell’s PATH, in which case point command at the absolute path to npx.
The server appears but has no tools
That is the connection working and the catalogue being empty. Either Abilities Manager is not installed — MCP Manager will serve an empty catalogue quite happily — or the abilities exist but are not exposed to this particular server. Open AcrossAI → MCP, select the server, and check its Tools and Abilities tabs. After changing what a server exposes, restart Antigravity: MCP clients receive their tool list once, at connection time.
Authentication fails, or it worked yesterday and stopped today
Application Passwords are shown once and are not your login password. Generate a fresh one from Quick Connect rather than retyping an old one, and copy it complete with spaces. If the request is being refused rather than failing, check the server’s access rules — a new server requires manage_options until you add a rule, and the gate fails closed. Access is also re-checked on every request, so a change to your role or capability takes effect immediately and a saved config does not keep working.
Connect a different AI client
The same server works with every MCP client — only the config file and top-level key change. See the guides for Gemini CLI, Claude Desktop, Claude Code, Cursor, VS Code, GitHub Copilot, Windsurf, Zed, Codex and every other client.
Not installed yet?
Install MCP Manager on your site, then come back and run Quick Connect.