sqry-antigravity

sqry for Antigravity

Use this skill to configure Google Antigravity (the IDE and the agy CLI) for sqry v33.0.1 MCP-backed semantic code search.

Setup

Install or upgrade sqry:

curl -fsSL https://raw.githubusercontent.com/verivus-oss/sqry/main/scripts/install.sh | bash -s -- --component all
sqry --version
sqry-mcp --version
sqry-lsp --version
sqryd --version

Index the project:

cd /path/to/your/project
sqry index .
sqry index --status --json .

Open Antigravity's MCP config. In the IDE: click the "..." menu in the Agent panel, choose MCP Servers, then Manage MCP Servers, then View raw config; this opens mcp_config.json. (Alternatively, Settings, then Customizations, then Open MCP Config.) The file is often at ~/.gemini/config/mcp_config.json, which Antigravity shares with the Gemini CLI; some IDE installs use ~/.gemini/antigravity/mcp_config.json. Use "View raw config" to open whichever file is active. sqry mcp setup has no Antigravity target; write the entry by hand.

Antigravity uses a single mcpServers object. A local (stdio) server takes a string command plus an args array and an env object:

{
  "mcpServers": {
    "sqry": {
      "command": "/absolute/path/to/sqry-mcp",
      "args": ["--no-daemon"],
      "env": {
        "SQRY_MCP_WORKSPACE_ROOT": "/path/to/your/project"
      }
    }
  }
}

(For remote HTTP servers Antigravity uses serverUrl, not url; not needed for sqry's local stdio server.)

Save the file; Antigravity reloads MCP configuration automatically. If it does not pick up the change, restart Antigravity.

Config collision: Antigravity and Gemini CLI may share ~/.gemini/config/mcp_config.json. If you also use sqry-gemini, both hosts read the same sqry entry. That is usually fine, but verify workspace roots do not pin the wrong repo; omit SQRY_MCP_WORKSPACE_ROOT when one entry serves several repos.

Antigravity also supports Agent Skills across its IDE and CLI, so this skill set can be installed into Antigravity directly as well as configured as an MCP server.