Time to Move

If you are following Google news closely you are probably aware about Antigravity CLI announced on the Google I/O 2026 and gradual move to the new tools ecosystem from the previous generation of AI assistants. In short, it’s time to move from Gemini CLI to Antigravity CLI. In this article I’ll explain how to set up your essential MCP servers for Google Cloud in the Antigravity CLI.

Gemini CLI MCP Configuration

Everybody has their own set of extensions and tools for Gemini CLI. In my case, I work extensively with Google Cloud databases and, as such, I have a few “must-have” extensions for Gemini CLI.

Here is my minimum Gemini CLI configuration for MCP servers.

gleb@db-connect:~$ gemini extension list
Ignore file not found: /home/gleb/.geminiignore, continue without it.
✓ alloydb (1.0.0)
 ID: dffab4e5e5d86ea81431cad2bf77fc027c0042d54fc4414c67145bfa255ee6cf
 name: dffab4e5e5d86ea81431cad2bf77fc027c0042d54fc4414c67145bfa255ee6cf
 Path: /home/gleb/.gemini/extensions/alloydb
 Enabled (User): true
 Enabled (Workspace): true
 MCP servers:
  AlloyDB MCP Server

✓ cloud-sql (1.0.0)
 ID: fe4d062a1349d2dddc18bd27899586f9c5a6ea524a95c44ec45257cbd18e9ed9
 name: fe4d062a1349d2dddc18bd27899586f9c5a6ea524a95c44ec45257cbd18e9ed9
 Path: /home/gleb/.gemini/extensions/cloud-sql
 Enabled (User): true
 Enabled (Workspace): true
 MCP servers:
  Cloud SQL MCP Server

✓ developer-knowledge (0.1.0)
 ID: 7b4042e11865c674ad1b7007c3040ba4a2a277c16c8d9bda9ba10ac7a70d2eec
 name: 47ba5f7123468475fe1edc973bf455cabe8eb51061f1e892d0bb9e1867db98b9
 Path: /home/gleb/.gemini/extensions/developer-knowledge
 Source: https://github.com/gemini-cli-extensions/developer-knowledge (Type: git)
 Enabled (User): true
 Enabled (Workspace): true
 Context files:
  /home/gleb/.gemini/extensions/developer-knowledge/GEMINI.md
 MCP servers:
  developer-knowledge

✓ spanner (1.0.0)
 ID: eb1ea9d72fe0c79269a8dc2b047ddfb531b004ed19afb45eaef9e9a38cccf351
 name: eb1ea9d72fe0c79269a8dc2b047ddfb531b004ed19afb45eaef9e9a38cccf351
 Path: /home/gleb/.gemini/extensions/spanner
 Enabled (User): true
 Enabled (Workspace): true
 MCP servers:
  Spanner MCP Server
Enter fullscreen mode Exit fullscreen mode

There are three extensions for different Google Cloud databases and the Developer Knowledge MCP. For some projects I have additional MCP servers depending on the nature of the project, but for this tutorial, we will limit ourselves to just those four extensions. Our goal is to move everything to Antigravity CLI and get them working.

Install Antigravity CLI

The full instructions on how to install Antigravity CLI are in the documentation, but here is a short version. I am showing this on a Debian Linux box ,but the steps are generally the same for a Mac installation and migration.

Run the installation script in a terminal window on your Mac or Linux machine.

curl -fsSL https://antigravity.google/cli/install.sh | bash
Enter fullscreen mode Exit fullscreen mode

At the end of the installation, it should show something like this:

On Linux, it automatically adds an alias for the binary, so you can start the tool using the agy alias. On the first launch, it will ask you to authenticate either with your Google account or by using a specific project.

And if you’ve chosen a project path then after authentication it will ask to put the project ID:

Next, it will ask about your location and then prompt you to choose a color scheme. On the color scheme screen, there’s a checkbox at the bottom that allows you to import all your existing Gemini CLI extensions into Antigravity CLI.

And as you can see, all my existing extensions are listed there. Can we wrap up here and call it a day? We could, but what if we missed the checkbox and clicked ‘Next’ without importing our extensions? As a result, we wouldn’t have any of our old MCPs in our Antigravity CLI.

Is it possible to migrate them afterward? Yes, of course, and in the next section, we’ll do exactly that.

Migrating Extensions to Antigravity Plugins

The full guide for migrating Gemini CLI extensions is in the documentation and you can take a look there if something isn’t working or if you want the latest information and updates. Here is my short version, along with a few fixes I had to apply.

First, exit Antigravity and run the following command in the terminal:

agy plugin import gemini
Enter fullscreen mode Exit fullscreen mode

The command should find all existing extensions, skills, hooks, and MCP servers and convert them into Antigravity plugins. You should see something like this:

Now you can start the Antigravity CLI and check your MCP servers using the /mcp command. All of your MCP servers should be visible in the output.

At first glance, it looks like everything is fine. But you’ll notice that only the Developer Knowledge MCP shows its tools, while none of the database plugins show any tools at all. If that happens, you might need to fix your configuration.

Have a look into the tools definitions in the ~/.gemini/antigravity-cli/mcp directory — the tools don’t have parameters.

gleb@db-connect:~$ cat .gemini/antigravity-cli/mcp/AlloyDB\ MCP\ Server/list_clusters.json | jq
{
  "name": "list_clusters",
  "description": "List all clusters",
  "parameters": null
}
Enter fullscreen mode Exit fullscreen mode

Also, if we check the Antigravity CLI log at ~/.gemini/antigravity-cli/cli.log, we can see that the database MCP servers are not authenticating correctly.

W0618 18:12:18.733858 86343 mcp_auth.go:634] OAuth setup failed for Spanner MCP Server: OAuth client ID required: server does not support dynamic client registration
W0618 18:12:18.734186 86343 mcp_auth.go:634] OAuth setup failed for AlloyDB MCP Server: OAuth client ID required: server does not support dynamic client registration
W0618 18:12:18.740350 86343 mcp_auth.go:634] OAuth setup failed for Cloud SQL MCP Server: OAuth client ID required: server does not support dynamic client registration
W0618 18:12:18.917512 86343 mcp_auth.go:634] OAuth setup failed for developer-knowledge: OAuth client ID required: server does not support dynamic client registration
Enter fullscreen mode Exit fullscreen mode

And when we look into the plugin config for the imported AlloyDB MCP extension, we can see it doesn’t have an authentication section. Also, the plugin’s name consists of several words separated by spaces.

gleb@db-connect:~$ cat .gemini/config/plugins/alloydb/mcp_config.json 
{
  "mcpServers": {
    "AlloyDB MCP Server": {
      "command": "",
      "args": null,
      "cwd": "",
      "env": null,
      "serverUrl": "https://alloydb.googleapis.com/mcp"
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

The authProviderType parameter is missing, and the name for the MCP server should be fixed. This is likely why it isn’t working correctly. Let’s rename the MCP server and add the missing parameter. Here is the fixed configuration for the AlloyDB MCP plugin:

{
  "mcpServers": {
    "AlloyDB": {
      "command": "",
      "args": null,
      "cwd": "",
      "env": null,
      "serverUrl": "https://alloydb.googleapis.com/mcp",
      "authProviderType": "google_credentials"
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Now, if we start the Antigravity CLI again and run the /mcp command, we can see all the tools associated with the remote AlloyDB MCP.

And when we test the MCP, we can confirm that it works correctly now.

We now have a new subdirectory for the AlloyDB MCP server, and the tools have all the necessary parameters and required information there.

gleb@db-connect:~$ cat .gemini/antigravity-cli/mcp/AlloyDB/list_clusters.json | jq
{
  "name": "list_clusters",
  "description": "List all clusters",
  "parameters": {
    "description": "Message for requesting list of Clusters",
    "properties": {
      "filter": {
        "description": "Optional. Filtering results",
        "type": "string"
      },
      "orderBy": {
        "description": "Optional. Hint for how to order the results",
        "type": "string"
      },
      "pageSize": {
        "description": "Optional. Requested page size. Server may return fewer items than requested. If unspecified, server will pick an appropriate default.",
        "format": "int32",
        "type": "integer"
      },
      "pageToken": {
        "description": "A token identifying a page of results the server should return.",
        "type": "string"
      },
      "parent": {
        "description": "Required. The name of the parent resource. For the required format, see the comment on the Cluster.name field. Additionally, you can perform an aggregated list operation by specifying a value with the following format: * projects/{project}/locations/-",
        "type": "string"
      }
    },
    "required": [
      "parent"
    ],
    "type": "object"
  }
}
Enter fullscreen mode Exit fullscreen mode

The old subdirectory with the incomplete tools can now be removed from the MCP directory.

gleb@db-connect:~$ rm -rf .gemini/antigravity-cli/mcp/AlloyDB\ MCP\ Server/
Enter fullscreen mode Exit fullscreen mode

We can fix the rest of our MCP servers for Cloud SQL and Spanner in the same way. For the Developer Knowledge MCP, however, we only need to add the authProviderType, its name didn’t have any spaces and was processed correctly.

In the end, you should see something like this when you list your MCP servers in the Antigravity CLI:

And a couple of words about the Developer Knowledge MCP. I think it’s one of the “must-have” MCPs in any configuration. It provides up-to-date information directly from the Google documentation and is one of the tools I use every single day.

You can also test the Developer Knowledge MCP by asking it to prepare a tutorial on a specific product option. For example, you can ask: ‘Prepare a tutorial with options on how I can connect to an AlloyDB instance.’ The Developer Knowledge MCP will use the search_documents tool to find the information and then create the tutorial based on the latest version of the Google documentation.

Try it and let us know

I recommend Antigravity CLI to everyone who likes command-line tools and is more comfortable with a terminal than a GUI. But keep in mind that Antigravity also has a GUI application and IDE, so you have a choice.

If you need to customize your Antigravity setup, it supports skills, plugins, rules, hooks, and MCP servers.

Happy migration, and let us know how it works for you!