Recipe

Antigravity with Stable Baseline.

Add Stable Baseline to Antigravity's MCP config, sign in from the browser, and ask its agent to document your repository.

1. Add the server

ForFile
Every workspace~/.gemini/config/mcp_config.json
This workspace.agents/mcp_config.json
mcp_config.jsonjson
{
  "mcpServers": {
    "sb": {
      "serverUrl": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp"
    }
  }
}

serverUrl, not url

Antigravity only reads serverUrl for a remote server. A config that says url is ignored.

Antigravity signs you in to Stable Baseline in your browser when it first connects.

Or use an API key

Create one under Organisation settings, Developers, API keys. See Setup. Add it as a header:

mcp_config.jsonjson
{
  "mcpServers": {
    "sb": {
      "serverUrl": "https://api.stablebaseline.io/functions/v1/cloud-serve/mcp",
      "headers": {
        "Authorization": "Bearer your_key"
      }
    }
  }
}

Keep the key out of shared files

Put a key only in the file in your home folder, never in the workspace's .agents folder that goes into git. For a shared workspace config, use the sign-in version above. Keep the key itself in a secret store, such as the STABLE_BASELINE_API_KEY environment variable, when you are not using it.

2. Document the repository

Ask Antigravity's agent in plain words:

prompt
Document this repository in my Stable Baseline project. Use the Stable Baseline tools to find my workspace and project (do not create them), read the code, design a structure of folders, documents and diagrams, write them, and add a Stable Baseline section to AGENTS.md so you keep the docs current as the code changes.

It follows the same steps as the sb-setup prompt:

  1. Checks the connection

    It confirms it can reach Stable Baseline with your key or sign-in.
  2. Finds your workspace and project

    It never creates them: if it cannot find the ones you mean, it asks you to create them in the app first.
  3. Remembers them

    It writes their ids to .sb/config.json, and keeps .sb/ out of git.
  4. Checks for existing docs

    If the project already has documentation, it asks whether to add to it, replace it, or stop.
  5. Reads the repository

    It works through the code to understand what is there.
  6. Designs a structure

    Folders and documents that fit this repository, not a fixed template.
  7. Writes it

    Folders, documents, and the diagrams each document needs.
  8. Updates AGENTS.md

    It adds a Stable Baseline section with rules for keeping the docs current, and keeps everything else in the file.
  9. Sums up

    It tells you what it created.

3. Try it

  • “What changed in the checkout service this week? Update its document.”
  • “Add a sequence diagram of the sign-in flow to the authentication document.”
  • “Create a plan for the database migration with three phases.”
  • “Log a risk in the work register: the payment provider's rate limits.”