Google agent IDE, Native OAuth

Antigravity IDE WordPress MCP. Set it up from the agent panel.

Antigravity IDE WordPress MCP setup happens in the agent side panel rather than a terminal, and the IDE adds something the CLI cannot: a browser agent that can open the page WordPress just changed. The server itself is stored in the same mcp_config.json the CLI uses, so there is nothing to redo if you already configured agy.

Get GoBuildWP free Setup steps

Checked against Antigravity IDE's documentation on 29 September 2026, entries from GoBuildWP Free 1.18.6

By GoBuildWPContent updated 13 October 2026How we check claims

~/.gemini/config/mcp_config.jsonOAuth 2.1

{
  "mcpServers": {
    "gobuildwp-your-site-com": {
      "serverUrl": "https://your-site.com/wp-json/mcp/wppilot-oauth"
    }
  }
}

Open with: Agent panel menu, MCP Servers
Raw file: View raw config
Shared with: Antigravity CLI

Setup

Add WordPress from the agent panel

The IDE is for work you watch: build a page, look at it, adjust. Configure it once and reuse across workspaces.

Open MCP Servers
Click the menu at the top of the editor's agent side panel and choose MCP Servers, then Manage MCP Servers.
View raw config
Choose View raw config to open mcp_config.json, and paste GoBuildWP's serverUrl block. Servers from the MCP Store install with a hover and Install instead; GoBuildWP is a custom server, so it goes in by hand.
Name it after the site
The IDE keeps servers across workspaces. If you manage several WordPress sites, name each server after its site so the agent never reaches for the wrong one.
Sign in
Sign in when the IDE asks for the new server, as a WordPress user made for this work. The grant is shared with the CLI.
Ask for discovery
In a new agent conversation, ask it to list the WordPress server's tools before giving it a task.

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.

First connection checkRead Only

Use the gobuildwp-your-site-com MCP server in Antigravity IDE. 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.

First task

A first look-and-report task

This uses the IDE's browser agent alongside WordPress reads. Nothing is edited.

Antigravity IDE promptReads only

Use the WordPress MCP server and the browser. Read only.

1. wppilot/search-content for the home page.
2. wppilot/get-page-view-link for it; open the link
   in the browser and describe the first screen.
3. wppilot/audit-accessibility on the same page.
4. Match each finding to what you saw.

Inside Antigravity IDE

Using the browser agent as the check

The Manage MCP Servers view shows configured servers. The more convincing check is visual: ask the agent to call wppilot/get-page-view-link and open the result with the browser agent. If the page it describes matches what you see, the connection, the user's permissions and the site all agree.

The IDE has its own tool permission prompts, and GoBuildWP enforces WordPress capabilities, the safety profile and confirmation on top. They are two separate systems; approving a tool in the IDE does not widen what the WordPress user can do.

Community reports describe a cap of about 100 MCP tools in the IDE; Google's docs do not state one. If the WordPress tools stop appearing after adding other servers, disable abilities you do not use with disabledTools. Google also notes that Enterprise customers cannot use Antigravity IDE.

Signs it worked

The server appears under Manage MCP Servers
The agent lists wppilot/ tools
The browser agent opens the page view link
Writes are refused on Read Only

Connect screen

The IDE's entry, and where the IDE opens it

GoBuildWP generates the serverUrl entry for the IDE exactly as for the CLI. Its access-token hint names the IDE's own route to the file: the … menu at the top of the agent side panel, MCP Servers, Manage MCP Servers, View raw config. Guides that say Settings, Customizations, Open MCP Config describe the separate Antigravity 2.0 desktop app, not the IDE.

OAuth 2.1	serverUrl alone, then sign in when the IDE asks. Tokens are shared with the CLI.
Access token	serverUrl plus headers, for a WordPress user shared by a team or a site without working OAuth.
Application Password	The npx bridge as a stdio entry.

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.

~/.gemini/config/mcp_config.jsonAccess token

{
  "mcpServers": {
    "gobuildwp-your-site-com": {
      "serverUrl": "https://your-site.com/wp-json/mcp/wppilot",
      "headers": {
        "Authorization": "Bearer wpp_YOUR-ACCESS-TOKEN"
      }
    }
  }
}

Seeing changes land

Watch an Elementor edit land with the browser agent

The IDE's advantage is that it can look. On a staging site set to Production Safe, ask the agent to change one Elementor heading and then open the page it changed. wppilot/elementor-find-elements locates the element by widget type or text and returns its ID, wppilot/elementor-edit-element merges the new settings onto it and validates them on the server, and wppilot/get-page-view-link gives the browser agent a URL and the viewport widths worth checking.

An unpublished page's preview needs an authorized browser session. Use an existing authorized session, normal WordPress login or open it yourself. wppilot/create-admin-access-link is the ability-provided login route, a critical operation that Production Safe refuses; it is not the only way to sign in. If Elementor Pro's element cache serves an old heading after the saved edit is verified, wppilot/elementor-clear-document-cache clears it for that document.

"Find the heading that says Our services with wppilot/elementor-find-elements and change its text to What we do."
"Get the view link, open it in the browser at mobile and desktop widths, and describe the heading in each."
"Show the ledger entry for the edit and whether it can be rolled back."

Staging and production side by side in one workspace

Because the global and workspace config files are shared with the CLI, a common setup is the production site in the global file and the staging site in the workspace's .agents/mcp_config.json, each named after its host. Give them different access. The staging entry can use OAuth as an administrator account set aside for the IDE. The production entry is safer as an access token capped at Read Only, so the IDE can compare the two sites but cannot change production, whatever the agent decides mid-task.

Accessibility fixes the IDE can check by eye

The first IDE task pairs wppilot/audit-accessibility findings with what the browser agent saw. Some of those findings are content fixes an agent can make on staging: missing alt text is set with wppilot/update-image-alt after the agent has looked at each image with wppilot/get-media-image, and the audit run again on the same URL should no longer list them. Others, such as heading order or a missing skip link, live in the theme or the page layout and are better fixed in code or in the builder by a person.

Ask the browser agent to reopen the page after each change rather than trusting the audit alone. The audit reads the HTML a logged-out visitor receives, and the browser shows what that HTML looks like; the two together are stronger evidence than either one.

Antigravity IDE and GoBuildWP Cloud

Antigravity, editor and CLI, is on the list of apps that sign in to the optional GoBuildWP Cloud with OAuth, using the same serverUrl key. One Cloud entry can stand in for several site entries, and Cloud lets you mark the IDE's connection read-only even on sites connected as Production Safe. Keep a direct entry when the site is only reachable from your machine: Cloud calls sites over the internet.

FAQ

Antigravity IDE questions

Does Antigravity IDE use the same config as the CLI?

Yes. Google documents one global mcp_config.json and one workspace .agents/mcp_config.json shared across Antigravity tools.

Why add WordPress to the IDE rather than the CLI?

When you want to see results: the IDE's browser agent can open the page an ability changed, which the terminal cannot.

Is GoBuildWP in the Antigravity MCP Store?

No. GoBuildWP runs on your own site, so it is added as a custom server with your site's URL.

Troubleshooting

Antigravity IDE errors and their causes

Symptom	Cause and fix
Settings, Customizations has no Open MCP Config	That path is from the Antigravity 2.0 desktop app. In the IDE, use the agent panel menu, MCP Servers, Manage MCP Servers, View raw config.
The wrong site answers	Two servers from different sites are both enabled. Rename them after their sites and disable the one you are not using.
Entry saved but ignored	It uses url instead of serverUrl.
WordPress tools missing after adding more servers	Too many tools across servers. Trim with disabledTools on the WordPress entry.

Antigravity CLI: the same server, scripted from agy with permission rules
Antigravity IDE walkthrough: the same steps in the documentation
Devin Desktop: the other IDE that uses serverUrl

Every client guide (26)

Antigravity IDE documentation read on 29 September 2026

Watch WordPress change from Antigravity IDE.

Add the server from the agent panel, sign in, and let the browser agent check each page.

Get GoBuildWP free See Pro pricing