Set up Antigravity

This guide configures the Versalist command-line interface (CLI). It also configures the Model Context Protocol (MCP) when Antigravity supports it.

Requirements

• Node.js 18.17 or later
• npm
• An account or provider credential for Antigravity
• A Versalist account
• A Versalist application programming interface (API) key with the required scopes

1. Install Antigravity

curl -fsSL https://antigravity.google/cli/install.sh | bash

• The install script supports macOS and Linux and installs the agy command.
• Use the official getting started guide for Windows installation.
• Antigravity CLI replaces Gemini CLI for Google AI Pro, Ultra, and free accounts.

2. Authenticate Antigravity

Authenticate Antigravity with its account or model provider. This credential is separate from your Versalist key.

agy
# agy opens a browser for Google sign-in when it finds no stored session.

1. Complete the Google sign-in flow in the browser.
2. Over SSH, open the printed address and paste the authorization code into the terminal.
3. To use a Gemini API key, set "modelProvider": "gemini" in ~/.gemini/antigravity-cli/settings.json and export GEMINI_API_KEY.

3. Create a Versalist key

If you are already signed in, open API key settings. Create one key for this agent.

1. Name the key for Antigravity and its environment.
2. Select only the scopes that your workflow requires.
3. Copy the key before you close the dialog.
4. Store the key in a password manager or secret manager.
5. Load the key into the agent process environment.

The key page can select all five scopes. This agent path needs the first three. Skill scopes belong to vskill.

• Use read:challenges to browse or start challenges.
• Use submit:solutions to submit a solution.
• Use read:submissions to read submission history through MCP.
• Use read:skills / write:skills only if this agent will also run the Skill Exchange server.

Remove a scope if your workflow does not use it.

export VERSALIST_API_KEY=vk_live_...
test -n "$VERSALIST_API_KEY" && echo "Versalist API key is set"

4. Install the Versalist CLI

npm install -g @versalist/cli
versalist --help

Use npx -y @versalist/cli if you do not want a global installation.

5. Connect Versalist

Add the Versalist MCP server to ~/.gemini/config/mcp_config.json. Keep the key out of project files.

{
  "mcpServers": {
    "versalist": {
      "command": "npx",
      "args": ["-y", "@versalist/cli", "mcp"],
      "env": {
        "VERSALIST_API_KEY": "<VERSALIST_API_KEY>"
      }
    }
  }
}

Tool names and inputs: Versalist MCP server.

• The user file applies to every project. The Antigravity IDE reads the same file.
• Antigravity CLI does not document environment interpolation for this setting.
• Put the key only in the user file.
• Do not put a key in .agents/mcp_config.json or source control.

6. Launch Antigravity

Open the project directory in a trusted terminal. Then start the agent.

agy

7. Run the Versalist workflow

versalist list --search "agentic code optimization"
versalist start agentic-code-optimization-review

versalist run --command "python agent.py" --label baseline
versalist evaluate --run <baseline-run-id> --command "pytest" --score 70

versalist run --command "python agent.py" --label candidate
versalist evaluate --run <candidate-run-id> --command "pytest" --score 84

versalist compare --baseline <baseline-run-id> --candidate <candidate-run-id>
versalist submit --url https://github.com/you/solution --title "Candidate run"

The versalist start command loads challenge files. It does not launch the coding agent.

The example python agent.py command is a placeholder. Replace it with your agent command.

Verify the setup

Use these read-only checks before you start a challenge.

agy --version
# In Antigravity CLI, enter /mcp and confirm that versalist is connected.

Confirm that the host reports the Versalist server or command. Do not run a write tool only to test the connection.

Limitations

• Antigravity CLI does not document environment interpolation in MCP server settings.
• The .agents/mcp_config.json file must not contain a Versalist key.
• Antigravity CLI asks for approval before it runs an MCP tool that has no permission rule.
• Antigravity CLI authentication does not authenticate the Versalist command-line interface.
• The CLI stores local run evidence under .versalist/.
• The CLI does not upload local evidence automatically.
• The submit command sends metadata and URLs, not .versalist/ contents.

Revoke access

1. Open API key settings.
2. Find the key by name and last-use time.
3. Revoke the Versalist key.
4. Delete the versalist entry from ~/.gemini/config/mcp_config.json.
5. Enter /logout in Antigravity CLI if you must remove the Google session.
6. If you use a Gemini API key, remove GEMINI_API_KEY from the agy process environment.
7. Remove VERSALIST_API_KEY from the process environment.
8. Restart the agent process.

Revoke the provider credential separately if it is exposed. A Versalist key revoke does not revoke the provider credential.

Official documentation

Use these official sources if the vendor changes a command or setting.

• Antigravity getting started
• Antigravity CLI authentication
• Antigravity MCP
• Antigravity CLI reference
• Migrate from Gemini CLI

Return to the coding agent index, or open the Versalist CLI reference.

Canonical guide: /docs/coding-agents/antigravity