Google terminal agent, Native OAuth
Antigravity CLI WordPress MCP. The terminal side of Antigravity.
Antigravity CLI WordPress MCP setup is the scriptable half of Google's Antigravity: you run agy in a terminal, keep the WordPress server in mcp_config.json, and decide in a permissions file which WordPress tools may run without asking. It shares that config file with Antigravity IDE, so a site added once is available in both.
Checked against Antigravity CLI's documentation on 29 September 2026, entries from GoBuildWP Free 1.18.6
{
"mcpServers": {
"gobuildwp-your-site-com": {
"serverUrl": "https://your-site.com/wp-json/mcp/wppilot-oauth"
}
}
}- Command
- agy
- Config
- ~/.gemini/config/mcp_config.json
- Remote key
- serverUrl only
Setup
Connect agy to WordPress
Coming from Gemini CLI? Servers used to live in ~/.gemini/settings.json. Antigravity reads mcp_config.json instead, and old WordPress guides for Gemini CLI now redirect here.
Choose global or workspace
~/.gemini/config/mcp_config.json makes the site available everywhere; .agents/mcp_config.json in a repository scopes it to that workspace, and can be committed when it holds only the OAuth URL.
Add the serverUrl entry
Paste GoBuildWP's block, or open the MCP Manager overlay with /mcp inside agy and add it there.
Sign in
The first connection to the OAuth URL starts the browser sign-in; the redirect returns through antigravity.google. Approve as the WordPress user the terminal should act as.
Write permission patterns
Keep the site Read Only. Use the installed client permission UI to authorize exact read tools after confirming their displayed names and supported syntax. Leave unmatched operations asking; do not grant a server-wide wildcard for the first test.
Pick a review level for scripts
The toolPermission setting accepts request-review (the default), proceed-in-sandbox, always-proceed and strict. Keep request-review for anything that touches a live site.
Verify the connection before allowing changes
Select Read Only explicitly; the default is Production Safe. Use a dedicated identity with manage_options on a single site, or superadmin on multisite. Match the named tool call, site URL and returned record ID against WordPress.
Use the gobuildwp-your-site-com MCP server in Antigravity CLI. Do not change anything.
1. Report the active GoBuildWP safety profile.
2. List the abilities this connection can see.
3. Call wppilot/get-site-settings and report the site URL and locale.
4. Call wppilot/list-content for the five newest pages,
then wppilot/get-content on one of them.
5. Name every ability you called and each WordPress ID you read.These setup instructions are not a recorded live-client test. Keep credentials out of repositories, logs and shared files.
Inside Antigravity CLI
Checking the server from the terminal
The /mcp overlay lists configured servers and is where a failed server shows up first. /config, also reachable as /settings, shows the settings in force, which helps when a workspace file is overriding the global one.
Google's Antigravity docs do not document a log file or debug flag for MCP. When the overlay reports a failure, the fastest cross-check is on the WordPress side: GoBuildWP's Connection Doctor, or the connection list on the Overview screen, which records whether the request ever arrived.
disabledTools on the entry hides WordPress abilities from the agent; disabled switches the whole server off without deleting it. Both are useful when one repository should see only content abilities.
Signs it worked
- /mcp lists the server without an error
- Client authentication status and a named authorized read agree with the expected site ID and server connection record
- Unruled WordPress tools ask before running
- A Gemini-era httpUrl entry is gone
First task
A first scripted-style task
The CLI is where repeatable jobs live. This one produces the same report every time, so you can compare runs.
Use the WordPress MCP server. Read only.
1. wppilot/audit-content, then wppilot/audit-content-status
until it finishes.
2. Count findings by type.
3. wppilot/list-changes: writes in the last 7 days.
4. Print both as plain text tables.Connect screen
The Antigravity CLI entries GoBuildWP writes
GoBuildWP writes the same entry for both Antigravity clients: mcpServers with serverUrl, pointing at the OAuth URL, or serverUrl plus an Authorization header for a token. That matches Google's docs, which say the legacy url and httpUrl fields are not supported. A Gemini CLI entry copied across uses httpUrl and is ignored without an error.
| OAuth 2.1 | serverUrl alone. Antigravity handles OAuth for servers that support dynamic client registration, and stores tokens in ~/.gemini/antigravity/mcp_oauth_tokens.json. |
|---|---|
| Access token | serverUrl plus headers. The better fit for scripted runs where no browser is available. |
| Application Password | A stdio entry running the npx bridge with credentials in env. |
Endpoints on your site: /wp-json/mcp/wppilot-oauth for OAuth, /wp-json/mcp/wppilot for tokens and passwords. Through the optional GoBuildWP Cloud instead, every client uses https://app.gobuildwp.com/mcp with the server name gobuildwp, and a personal Cloud token is read from GOBUILDWP_TOKEN where the client supports environment variables.
{
"mcpServers": {
"gobuildwp-your-site-com": {
"serverUrl": "https://your-site.com/wp-json/mcp/wppilot",
"headers": {
"Authorization": "Bearer wpp_YOUR-ACCESS-TOKEN"
}
}
}
}Troubleshooting
Antigravity CLI errors and their causes
| Symptom | Cause and fix |
|---|---|
| The server entry is ignored | It uses url or httpUrl. Antigravity accepts serverUrl only. |
| Servers from ~/.gemini/settings.json vanished | Antigravity reads ~/.gemini/config/mcp_config.json. Move the entries and rename httpUrl to serverUrl. |
| OAuth does not start | Check /.well-known/oauth-authorization-server on the site returns JSON, since Antigravity relies on dynamic client registration. |
| Every WordPress call asks for approval | Expected with no rule. Add mcp(server/tool) rules for reads only. |
agy as a repeatable site job
Turn the report into a weekly Antigravity CLI run
The first agy task prints the same tables every time, which is the point: run it weekly and the differences are the news. Two details make that dependable. A background audit started with wppilot/audit-content keeps its findings for seven days after the job ends, so a run that is interrupted can pick the results up with wppilot/audit-content-status instead of starting again. And the ledger half of the report is better served by wppilot/export-changes with since and until set to the week, which returns flat rows with the ability, the agent behind each write and whether it can still be undone.
For a run nobody watches, give agy its own GoBuildWP access token rather than your OAuth grant: capped at Read Only, limited to the audit and change-log abilities, with an expiry you renew deliberately. Put it in the entry's headers and keep the token file out of the repository. A read-only job writes nothing, so it adds no change-ledger entries; its activity shows as the token's last-used time on the Connect screen. If the job ever writes, those entries carry the token's name, so it is easy to tell apart from people working on the site.
- "Call wppilot/export-changes since last Monday until today. Group the rows by agent and by ability."
- "Compare this week's audit counts with the table in reports/last-week.txt and list only what changed."
Which WordPress tools to allow without a prompt
Permission rules in agy decide which calls run without asking, and GoBuildWP decides which calls are allowed at all. Use the first for convenience and the second for safety. A sensible allowlist for an unattended report covers reads only: listing and getting content, the content audit and its status, the change list and the export. Leave every write unruled so it prompts, and remember that destructive abilities also require GoBuildWP's own confirmation. By default the agent can supply that flag itself; only the site's A person approves setting makes it wait for you.
If a job ever needs to write, prefer a separate entry with a separate token rather than widening the rules on the reporting entry. Two server names in mcp_config.json, one read-only and one for supervised changes, make it obvious from the /mcp overlay which one a session is using.
When a scheduled run that worked last week suddenly reports nothing, check the token before the site. An expired or deleted GoBuildWP token is refused on every call, and agy may simply show the server as failed in the overlay. Renew the token on the Connect screen, update the header, and run the report once by hand to confirm the tables come back before leaving it to the schedule again.
From Gemini CLI to agy, directly or through Cloud
Coming from Gemini CLI, the WordPress entry needs moving and one key renamed, httpUrl to serverUrl. If you would rather not maintain an entry per site, the optional GoBuildWP Cloud lists both Gemini CLI and Antigravity among the apps that sign in with OAuth. In mcp_config.json the Cloud link still goes under serverUrl, and after signing in you choose which connected sites agy may reach. A direct entry per site remains the route with no account and no relay, and the only one for a site that answers on your own machine alone, since Cloud reaches sites over the internet.
FAQ
Antigravity CLI questions
Is Antigravity CLI the replacement for Gemini CLI?
Google publishes a Gemini CLI migration guide for Antigravity CLI, and MCP servers move from settings.json to mcp_config.json with serverUrl. GoBuildWP's old Gemini CLI guide redirects here.
Do Antigravity CLI and IDE need separate WordPress setups?
No. Both read ~/.gemini/config/mcp_config.json and a workspace's .agents/mcp_config.json. What differs is the workflow: permissions and scripts here, a visual panel and a browser agent in the IDE.
Can agy run WordPress tools unattended?
With permission rules and a less strict toolPermission level, yes. Pair that with a GoBuildWP token limited to the abilities the job uses.
Related
The rest of Antigravity
- Antigravity IDE: the same server, used from the editor with a browser agent
- Moving from Gemini CLI: the migration checklist
- Qwen Code: a Gemini CLI fork that kept httpUrl
Antigravity CLI documentation read on 29 September 2026
Script WordPress work from agy.
serverUrl in mcp_config.json, one sign-in, and permission rules that let reads through.