Connect Gemini (Antigravity) to braXos¶
braXos Maestro works with Google Antigravity, Google's agent IDE and CLI, as a remote MCP server. Antigravity registers itself with the braXos identity service automatically, so there is nothing to pre-provision; setup takes a config entry and one browser sign-in.
Before you start
- A braXos account in your organization. Your administrator confirms which systems and tools are enabled for you.
- Antigravity installed from antigravity.google and signed in with your Google account.
- Your organization's Maestro URL, e.g.
https://maestro.braxos.com/mcp.
Add braXos Maestro¶
Antigravity reads MCP servers from ~/.gemini/config/mcp_config.json (all projects) or
.agents/mcp_config.json in a project. Add braXos Maestro:
Note
Antigravity requires the serverUrl key for remote servers. The url and httpUrl
keys used by other clients (and by the older Gemini CLI) are not recognized.
Restart Antigravity so it picks up the change.
Sign in¶
- Open Settings (Cmd+, on macOS, Ctrl+, on Windows/Linux) → Customizations.
- Click Authenticate next to braxos-maestro. Your browser opens the braXos sign-in.
- Sign in with your organization's identity provider (single sign-on where configured). Use your work identity here, even if Antigravity itself is signed in with a different Google account: braXos determines your organization from this sign-in.
- Review the consent screen and approve. It lists Offline access, which keeps you signed in without repeated prompts.
- The browser lands on an Antigravity page showing an authorization code. Copy it and paste it into Antigravity when prompted.
- Antigravity lists the braXos tools available to you.
Why do I paste a code?
Antigravity's sign-in callback is a Google-hosted web page rather than a listener on your computer, so the browser can't hand the result back to the app directly. The code you paste is a one-time value: it expires within about a minute, can be used only once, and is bound to a secret that only your Antigravity instance holds, so it is useless to anyone else. Don't share it while it is still valid.
Each Antigravity surface signs in separately. The IDE and the agy CLI keep their own
tokens; authenticate braxos-maestro once in each surface you use.
Authentication¶
Antigravity authenticates with OAuth 2.0 against the braXos identity service, as Claude and Copilot do: you sign in as yourself, Maestro derives your organization and group memberships from your token, and the tools you can see and call are filtered by your group permissions. Credentials for the downstream systems (Google, Jira, Salesforce, …) stay server-side and are never exposed to Antigravity or the model.
See Security & tenancy for the full model.
Troubleshooting¶
| Symptom | Likely cause | Fix |
|---|---|---|
| braxos-maestro doesn't appear under Customizations | Config not read, or the wrong key | Check the file location and use serverUrl; restart Antigravity |
| Sign-in fails before the braXos login page | Registration not permitted for Antigravity | Contact your braXos administrator |
| Pasted code is rejected | The code expired or was already used | Click Authenticate again and paste the new code promptly |
| Signed in but no tools | No tools enabled for your groups | Ask your braXos administrator to grant access |
| Google sign-in mentions Gemini Code Assist licenses | GOOGLE_CLOUD_PROJECT is set in your shell |
Start Antigravity without it, e.g. env -u GOOGLE_CLOUD_PROJECT agy |
The Gemini app and Gemini Enterprise
The consumer Gemini app (gemini.google.com) can add custom MCP servers for personal Google accounts only; work and school accounts are not yet supported. Organizations on Gemini Enterprise connect through its Custom MCP Server connector, which needs a pre-registered client: contact braXos to set one up.