Skip to content

Updated

Antigravity

Antigravity stores MCP configuration in a shared file at ~/.gemini/config/mcp_config.json that serves the Antigravity IDE, the agy CLI and Antigravity 2.0. A project-scoped alternative lives at .agents/mcp_config.json.

Gemini CLI uses a different settings file and schema. See the Gemini CLI guide when that is the client you run.

Install with the pinned CLI

CLI 0.2.14 has a matching installer for this client. Sign in first with npx -y lyrashield@0.2.14 login --oauth for local stdio. Review the planned changes before writing:

npx -y lyrashield@0.2.14 install antigravity --dry-run

When the preview is correct, run the installer:

npx -y lyrashield@0.2.14 install antigravity

The installer updates LyraShield's entry and preserves unrelated configuration. You can also use the manual snippet below. Restart or reload the client and complete a read-only authenticated call; an installed config entry alone does not prove client discovery.

Prefer to see exactly what gets written or set it up without Node.js? Configure it by hand below.

Local stdio setup

Add the following to ~/.gemini/config/mcp_config.json. Create the file if it does not exist. For project-scoped config, use .agents/mcp_config.json instead.

Manual fallback: merge the following into .agents/mcp_config.json. Recommended: run npx -y lyrashield@0.2.14 login --oauth once; the local MCP server reads the selected workspace credential from ~/.lyrashield/credentials.json. If you use an API key instead, set it in your private process environment before starting the client.

{
  "mcpServers": {
    "lyrashield": {
      "command": "npx",
      "args": [
        "-y",
        "@lyrashield/mcp@0.2.12"
      ],
      "env": {
        "LYRASHIELD_API_URL": "https://app.lyrashieldai.com"
      }
    }
  }
}
CLI installer for this client: Run this pinned command to add LyraShield's entry. The client-specific writer preserves unrelated configuration where supported.
npx -y lyrashield@0.2.14 install antigravity

Important gotchas

  • Antigravity uses `serverUrl`, not `url`, for HTTP servers — `url` is rejected.
  • This registry surface targets Antigravity IDE/2.0. The CLI uses `~/.gemini/antigravity-cli/skills` globally, while its project skills use `.agents/skills`.
  • Rules can live in `AGENTS.md`, `GEMINI.md` or `.agents/rules/*.md`; Antigravity 2.0 and the CLI also have distinct global rule directories.
  • Antigravity 2.0 and the IDE discover native plugins from `.agents/plugins/` or `~/.gemini/config/plugins/`; the Antigravity CLI installs a local package with `agy plugin install`. LyraShield's plugin artifact is prepared for direct installation, but no public listing or client runtime receipt is confirmed.

Remote endpoint

For Antigravity cloud environments that cannot run local processes, use serverUrl instead of command + args to connect to the remote Streamable-HTTP endpoint.

Gotcha — use serverUrl, not url: Antigravity uses serverUrl for HTTP-based MCP servers. The url field is rejected.
Skills and rules: Shared skills live in ~/.gemini/skills; project rules go in GEMINI.md (project) or AGENTS.md (global).

Manual fallback: merge the following into .agents/mcp_config.json. Complete OAuth in the client after adding the server. No API key belongs in this config.

{
  "mcpServers": {
    "lyrashield": {
      "serverUrl": "https://app.lyrashieldai.com/api/mcp"
    }
  }
}
Native OAuth: Antigravity detects LyraShield OAuth from this URL. Select Authenticate in Agent Settings, choose one workspace and approve the requested access once. Matching actions then run without another LyraShield review.

Verify the connection

Restart Antigravity and ask: "What LyraShield tools do you have access to?" to confirm the server is connected.

Local stdio requirements: Node.js 24+ and a LyraShield login. The @lyrashield/mcp package is published on npm, so npx -y @lyrashield/mcp@0.2.12 resolves directly.