Skip to main content

Connect tools

Connect Gemini CLI.

Give Gemini CLI access to the code connections Kin has recorded. Gemini CLI and Antigravity use separate settings, so check the instructions for the tool you use.

How this works in Kin

Do not assume one Google setup covers every Google product. Gemini CLI reads ~/.gemini/settings.json and Antigravity reads ~/.gemini/config/mcp_config.json, and Kin writes to each of them separately when it finds them.

Start with a disposable copy of your code. Examples below were checked on a specific build; language and workflow support are limited.

Check the example version and setup

Supported build

Every command below was run on Kin v0.7.6, macOS on Apple silicon, on 2026-09-09, against a four-file JavaScript repository created from scratch. The output shown is what that run printed. Current release: v0.7.19.

Before you start

  • Read /docs/agents first. Only the file differs, and here there are two of them.
  • Gemini CLI installed, so ~/.gemini/settings.json exists.
  • A repository admitted with kin init.

The steps

  1. 01

    Let setup write the entry

    Two Google products keep configuration under ~/.gemini and Kin writes to both when it finds both. They are separate clients with separate files, and configuring one does not configure the other.

    kin setup --intent agent
    Compare with the saved example output
      ✓ Gemini CLI configured (~/.gemini/settings.json)
  ✓ Google Antigravity configured (~/.gemini/config/mcp_config.json)
      bound to repository /private/tmp/docsverify-workflows/kin-orders

    One row per product Kin found. Gemini CLI gets the shared entry; Antigravity gets its own file and, like Codex CLI, is bound to the repository setup ran in.

  2. 02

    Read the Gemini CLI entry

    The shared JSON shape, in the settings file the CLI already keeps, not pinned to a repository.

    cat ~/.gemini/settings.json
    Compare with the saved example output
    {
  "mcpServers": {
    "kin": {
      "args": [
        "mcp",
        "start"
      ],
      "command": "/Users/troyfortinjr/.kin/bin/kin",
      "env": {
        "KIN_MCP_TOOL_PROFILE": "agent-default"
      }
    }
  }
}

    The entry sits beside whatever else that settings file holds. Antigravity reads ~/.gemini/config/mcp_config.json instead, and a workspace can carry its own .agents/mcp_config.json as well.

  3. 03

    Restart the client and check the server answers

    Setup already launched both entries and got an answer from each, so the remaining question is whether the client has reloaded.

    kin setup status
    Compare with the saved example output
      ✓ MCP: Gemini CLI            ok             mcpServers.kin present with agent-default profile (~/.gemini/settings.json)
  ✓ MCP: Google Antigravity    ok             mcpServers.kin present with agent-default profile (~/.gemini/config/mcp_config.json)

    A row per product. Two rows means two clients are configured, not that one was configured twice.

When the answer looks wrong

An empty or partial answer can reflect coverage, repository state, or an error. Each row below says what the state means and what to do next.

  • You configured one Google product and the other still shows nothing.

    They read different files. Gemini CLI reads ~/.gemini/settings.json; Antigravity reads ~/.gemini/config/mcp_config.json.

    Run kin setup --intent agent and let it write both, then read kin setup status.

  • Antigravity answers about the wrong repository.

    Its entry is pinned to the repository setup ran in.

    Run setup again from the repository you want, or edit the --repo value in its file.

  • Gemini CLI lists no Kin tools.

    It read its settings at launch.

    Start a new session, then run kin setup status to confirm the entry is still there.

Next action

Ask it a question you can check.

Pick a function you know, ask the agent for its callers, then run the same question on the command line and compare.

Find recorded callers