Antigravity is Google's AI development suite, and the way to use Gemini models with Katana. Connecting it lets you check stock, look up orders, and create or update records in plain language, using your live Katana data.

You can use Katana from either the Antigravity CLI or the Antigravity IDE. Setup is the same for both, and you only need to do it once. Antigravity connects through a configuration file on your computer rather than a settings page, so this guide is for people comfortable running a command in a terminal.

Before you start

You won't be able to connect Katana to Antigravity until these points are met:

On your computer

The Antigravity CLI or the Antigravity IDE is installed (whichever you prefer to work in).
- Both are at antigravity.google.
Node.js v18 or higher is installed.

In Katana

An active Katana account with the Access to MCP permission enabled.
- Account owners have it by default. For everyone else, an owner or a user with Manage users and permissions enables it: profile menu (top right) → Team → the user's name → Admin tab → check Access to MCP.
  - If your permission was just changed, refresh your Katana session before connecting.
  - No API key needed, just sign in with your normal Katana login, in the browser, once.

What the connection can do

Access to MCP is not limited by a user's other Katana permissions. Once it's on, the connected AI can read, create and update records across the account.

It can't delete anything. Read, create and update only. Deleting stays in Katana, with you.

Note: If you're using Gemini CLI, Google no longer supports it for individual accounts. Signing in returns a message directing you to Antigravity. Use the Antigravity CLI or IDE instead.

Step 1: Authorize Katana once in your terminal

Antigravity gives an MCP server around 15 to 30 seconds to start up, which isn't long enough to finish a browser sign-in. As such, signing in once from your terminal saves the token locally, and Antigravity then connects instantly afterward.

Open a terminal. On macOS that's Terminal or iTerm2, on Windows it's Command Prompt. If you're using the IDE, its built-in terminal works too (Ctrl + ` or Terminal → New Terminal).
Run:
npx -y mcp-remote@latest https://mcp.katanamrp.com
Your browser opens https://mcp.katanamrp.com/authorize.
Sign in to Katana and click Authorize.
When the browser says "Authorization successful! You may close this window and return to the CLI", close the tab and press Ctrl + C in your terminal to stop the process.

Step 2: Add Katana to your configuration file

The CLI and the IDE read the same file, so you only do this once:

macOS: ~/.gemini/config/mcp_config.json (in Finder, Cmd+Shift+G)
Windows: %USERPROFILE%\.gemini\config\mcp_config.json (in the Run dialog, Win+R)

Paste the block for your operating system and save. In the IDE you can open the same file from Settings → MCP Servers, or by pressing Cmd/Ctrl + P and typing mcp_config.json.

Configuration for macOS

{
  "mcpServers": {
    "katana": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.katanamrp.com"
      ],
      "env": {
        "PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin"
      }
    }
  }
}

Using NVM or a custom Node install?

If you get an executable file not found in $PATH error, run dirname $(which node) in your terminal. You'll get something like /Users/yourusername/.nvm/versions/node/v20.x.x/bin. Add that to the front of "PATH", or set "command" to the full path to npx, for example "/Users/yourusername/.nvm/versions/node/v20.x.x/bin/npx".

Configuration for Windows

{
  "mcpServers": {
    "katana": {
      "command": "cmd.exe",
      "args": [
        "/c",
        "npx",
        "-y",
        "mcp-remote@latest",
        "https://mcp.katanamrp.com"
      ]
    }
  }
}

Step 3: Connect

Pick whichever you work in. Both use the configuration you just saved.

In the terminal

Run agy and sign in with your Google account.
Type /mcp.

You'll know it worked when katana appears in the server list with a checkmark and its tools listed.

In the IDE

Open Manage MCP Servers and click Refresh, or restart Antigravity.

You'll know it worked when a green indicator appears next to katana.

Try your first prompt

Ask something you'd normally have to click through Katana for:

"Which bins hold SKU-1042, and what's in bin A-03-01 right now?"

For more examples of what you can ask, see the Katana MCP overview.

Staying in control

Ask it to show you the change first. Before you approve anything, ask it to summarize exactly what it's about to do. Check the products, quantities, prices, customers, suppliers, locations and statuses.
Verify in Katana. The AI is working from your live data, but it can still get something wrong. Check anything operational in Katana before you act on it.
Keep jobs scoped. Chat works best on a specific job: one order, one product line, this week. Loading a whole catalog is a job for Assisted import, not chat.
Reference SKUs, not product names. SKUs are what the AI matches reliably.
Katana only sends the data your question needs, and it goes to the AI provider you chose, under their terms.

Troubleshooting

Problem	Cause	What to do
This client is no longer supported for Gemini Code Assist for individuals	You're using the old Gemini CLI, which Google has deprecated for individual accounts.	Use the Antigravity CLI (`agy`) or the Antigravity IDE instead.
`context deadline exceeded`	The browser sign-in took longer than Antigravity's startup timeout, around 15 to 30 seconds.	Do step 1 in your terminal first, so the token is already saved before Antigravity starts the server.
`executable file not found in $PATH` (macOS)	Antigravity was launched outside your interactive shell, so it can't see your Node install.	Set `"PATH"` in the config block, or point `"command"` at the full path to `npx`. See the NVM tip in step 2.
`MCP Access permission required`	Your Katana user doesn't have the permission.	Ask your Katana account owner to enable Access to MCP, then refresh your Katana session.
Nothing happens, or `katana` never appears	The config was put in the wrong file.	Both the CLI and the IDE read `~/.gemini/config/mcp_config.json`. An older `~/.gemini/settings.json` is no longer used.
It connected before but now asks me to sign in again	The saved token expired or was cleared.	Run the step 1 command again to re-authorize.

Disconnecting Katana

The sign-in token is stored separately from the configuration, so removing Katana takes two steps:

Delete the katana block from mcp_config.json and restart Antigravity. This removes it from both the CLI and the IDE, since they read the same file.
Delete the saved token folder, ~/.mcp-auth/. Without this, the authorization remains active.

To stop someone from reconnecting through Antigravity or any other MCP client, also uncheck Access to MCP on their Katana user.

Your feedback is invaluable. Let us know your thoughts on this article or anything in Katana you'd like to see improved: [email protected]

How to connect Katana to Antigravity (Gemini)