Gemini CLI

For developers using the Gemini CLI.

Confirmed as of v0.45.0 · June 10, 2026

Valency Bond™ works with the Gemini CLI over MCP using OAuth.

Gemini CLI is retired for consumer accounts

Google stopped serving Gemini CLI requests for consumer accounts on June 18, 2026, in favor of the Antigravity CLI. The steps below still work if your organization has Gemini Code Assist Standard or Enterprise.

Prerequisites

• The Gemini CLI installed and working (gemini --version returns a version)
• You need a Valency account. Sign up here if you haven't already.

Setup

1. Install the Valency Gemini extension:

   gemini extensions install https://github.com/valency-oss/valency-gemini-extension --auto-update

   --auto-update keeps the extension current as new tools and fixes ship.

2. Start the Gemini CLI:

   gemini

3. Authenticate Valency:

   /mcp auth valency

   Sign in when the browser opens.

   Note

   Sign in with the email you used to register at app.valency.io. It does not have to match the email on your Google account.

4. Verify the connection:

   /mcp list

   valency appears as connected, with the Valency tools (paper search, author lookup, citation lookup, trend analysis, and more) listed.

5. Ask: "Search for papers about quantum computing" (more prompt ideas)

Success: You see paper results in your terminal. You can also explicitly invoke Valency tool calls.

Manual install (for environments where gemini extensions install is unavailable)

If you're on a corp-locked machine or otherwise can't use the extensions system, add the MCP server to your Gemini settings file directly:

• macOS / Linux: ~/.gemini/settings.json
• Windows: %USERPROFILE%\.gemini\settings.json

Merge the valency entry into the mcpServers block (alongside any others you already have):

{
  "mcpServers": {
    "valency": {
      "httpUrl": "https://labs.valency.io/mcp",
      "authProviderType": "dynamic_discovery",
      "oauth": {
        "enabled": true,
        "redirectUri": "http://localhost:33418/oauth/callback"
      }
    }
  }
}

Gemini registers itself automatically on first sign-in — you don't paste a client ID. (If you set one up before this changed, see Reconnecting.)

Then restart gemini and continue from step 3 above.

Skills

The Valency Gemini Skills extension layers seven multi-step research workflows on top of the MCP tools — profile, landscape, similar, trends, network, reading-list, and fresh-collaborators. Each one is a prescribed chain of tool calls, not a single search.

Install it alongside the connector:

gemini extensions install https://github.com/valency-oss/valency-gemini-skills --auto-update

Restart Gemini, then trigger a skill by slash command or natural language:

/valency:profile Yoshua Bengio
What should David Hogg be reading next?

Troubleshooting

Extension didn't install cleanly? Run gemini extensions list to confirm valency is present (the extension registers under that name, not the repo name). Reinstall with gemini extensions install https://github.com/valency-oss/valency-gemini-extension --auto-update if it's missing.

Browser didn't open or port 33418 is in use? Quit anything bound to that port and rerun /mcp auth valency.

Tools don't appear? Confirm /mcp list shows valency as connected. If auth completed but no tools appear, restart gemini so it picks up the new server connection.

Need to switch accounts? Open ~/.gemini/mcp-oauth-tokens.json (a JSON array of sign-in records) and delete the one whose "serverName" is "valency", then /mcp auth valency to sign in fresh. (That file holds the cached sign-in for every MCP server, so remove only the valency record rather than the whole file.)

---

Need help?

If something isn't working, check Troubleshooting for common fixes. See the FAQ for general questions, or report an issue if you're still stuck.