Google Antigravity | Integrations

Setup

Add Minds to Google Antigravity as a remote MCP server. Antigravity registers itself with the Minds OAuth server automatically, so you don't need a client ID or secret.

In Antigravity CLI, add the server from your terminal:

agy mcp add --type http minds https://getminds.ai/mcp

Or install the Minds plugin from the public minds-ai-co/minds-mcp repository. It bundles the same server entry:

agy plugin install https://github.com/minds-ai-co/minds-mcp

In Antigravity 2.0 or the Antigravity IDE, add the entry to ~/.gemini/config/mcp_config.json (all workspaces) or .agents/mcp_config.json (one workspace). In the IDE, open the file from the agent panel menu … → MCP Servers → Manage MCP Servers → View raw config. Remote servers use serverUrl; Antigravity does not accept url or httpUrl.

{
  "mcpServers": {
    "minds": { "serverUrl": "https://getminds.ai/mcp" }
  }
}

To sign in, open Settings (Cmd+, on macOS, Ctrl+, on Windows and Linux), go to Customizations and choose Authenticate next to minds. Sign in to Minds in the browser and choose Allow. Antigravity then shows an authorization code: copy it, paste it into the settings panel and choose Submit.

If you prefer an API key, or sign-in does not complete, create a key in Settings → API Keys and send it as a header instead:

agy mcp add --type http --header "Authorization: Bearer minds_YOUR_API_KEY" minds https://getminds.ai/mcp

In mcp_config.json, the same setting looks like this. Keep a file that contains a key out of version control.

{
  "mcpServers": {
    "minds": {
      "serverUrl": "https://getminds.ai/mcp",
      "headers": { "Authorization": "Bearer minds_YOUR_API_KEY" }
    }
  }
}

Antigravity asks before each Minds tool call by default. To approve all Minds tools at once, allow mcp(minds/*) in your permission policy. See the Antigravity MCP documentation for details.

MCP Server URL

https://getminds.ai/mcp

View full MCP documentation

Run audience research from an Antigravity agent

Antigravity agents can plan and run work across your workspace, so give them a written brief instead of a one-line prompt. Put the product concept, the audience you want to consult and the exact question wording in a file in the workspace, then ask the agent to list the available Minds tools and propose a Study from that brief. Check the Audience and the questions before you approve the run; the agent should not choose the research scope on its own.

Save the Study reference next to the brief so a colleague can open the same results later. When you compare variants, keep the Audience fixed and change only the stimulus you are testing. Keep API keys out of prompts, agent artifacts and committed files.