Connect Antigravity IDE to WordPress MCP
Add GoBuildWP to Antigravity IDE through MCP Servers, use global or workspace configuration, authenticate the remote endpoint, and verify permissions.
The IDE path suits work you are watching happen: building a page, checking the result, adjusting it. Because the editor holds the session, the management surface loads or edits a global or workspace MCP configuration file, and the credential you pick there is the one every request will carry until you change it. That makes it worth pointing at a dedicated WordPress user rather than your own administrator account, even for exploratory work.
What you will do 6 steps
Open MCP Servers
Choose Manage MCP Servers
View the raw config
Add GoBuildWP
Authenticate
Run a read-only test
Open the current MCP surface
In Antigravity IDE, open the agent side panel menu and select MCP Servers. Choose Manage MCP Servers, then View raw config when adding a custom remote server.
The global configuration lives at ~/.gemini/config/mcp_config.json. A workspace can use .agents/mcp_config.json so the server definition stays scoped to that project.
Use site-generated connection data
Choose Antigravity IDE in GoBuildWP's Connect screen and use the endpoint and authentication route generated by the installed site. Do not copy credentials from a public documentation example.
For a remote MCP connection, Antigravity uses serverUrl. Complete OAuth through the IDE's Authenticate control where available, or use the supported dedicated credential route generated by GoBuildWP.
Keep both permission systems visible
Antigravity has its own MCP permission controls and GoBuildWP enforces WordPress capabilities, safety profiles, individual ability status, rate limits, and critical confirmation. Configure both; neither automatically replaces the other.
Start with an inspect-only task. Expand access only after the team can see tool inputs, outputs, WordPress evidence, and the recovery path for a failed edit.
Questions this guide answers
Where does Antigravity IDE store the GoBuildWP connection?
In ~/.gemini/config/mcp_config.json globally, or .agents/mcp_config.json per workspace. Add it through the MCP Servers surface rather than hand-writing the file.
I manage several WordPress sites. What should I watch for?
The IDE keeps the connection open across projects, so a credential added while working on one site stays available while you are working on another. Name each connection after the site rather than after the client.
Does the IDE's own permission prompt replace GoBuildWP's controls?
No. They are two separate permission systems and both apply. The IDE decides whether the tool runs; the WordPress user's capabilities, the safety profile, the enabled abilities and the confirmation gates decide what it is allowed to do on the site.
Review noteRequirements and credential methods follow the shipped GoBuildWP source (WordPress 6.9+, PHP 8.0+). Client menus, account plans and third-party behaviour can change; use the installed version and live schema. Our evidence standard.