Guides3 min read

Gemini CLI

Connect Gemini CLI to OpsKnight over Streamable HTTP with /mcp auth or a personal access token header.

Status: Expected. These steps follow the Gemini CLI documentation; no end-to-end run of Gemini CLI against OpsKnight is recorded. Its OAuth profile (empty scope, redirect on localhost:7777) passed the emulated client matrix run.

Vendor documentation: MCP servers with the Gemini CLI (fetched 12 November 2026). That page notes that Gemini CLI was replaced by Antigravity CLI for unpaid-tier and Google One users on 18 June 2026; these steps apply where Gemini CLI is still in use.

Before you begin

  • An administrator has turned on AI assistant access in Settings → Integrations & ChatOps → MCP (AI Assistants) (see MCP setup).
  • Copy the MCP server URL from the Connect tab on that page; the examples below use https://ops.your-company.com/mcp.
  • You have your own OpsKnight account, Gemini CLI installed and a local browser.
  1. Add the server:

    bash
    gemini mcp add --transport http opsknight 'https://ops.your-company.com/mcp'
    

    Or in ~/.gemini/settings.json (all projects) or .gemini/settings.json:

    json
    {
      "mcpServers": {
        "opsknight": { "httpUrl": "https://ops.your-company.com/mcp" }
      }
    }
    

    Use httpUrl, not url: url selects the older SSE transport.

  2. Inside Gemini CLI, run /mcp auth opsknight, sign in to OpsKnight and approve the connection.

Gemini CLI discovers OpsKnight's authorization server from the 401 answer and registers itself; it needs a local browser and does not work headless. Tokens are stored in ~/.gemini/mcp-oauth-tokens.json.

If Automatic connections is off, an administrator registers a manual client and you add "oauth": { "enabled": true, "clientId": "<client id>" }.

Personal access token (alternative)

json
{
  "mcpServers": {
    "opsknight": {
      "httpUrl": "https://ops.your-company.com/mcp",
      "headers": { "Authorization": "Bearer okmcp_pat_…" }
    }
  }
}

The vendor page documents $VAR expansion for the env block but does not say whether it applies to headers, so this example uses the literal token. Keep that file private (it is in your home directory, not the project).

Verify the connection

  1. Run /mcp list (or gemini mcp list) and check the state of opsknight.
  2. Ask Gemini CLI "Who am I in OpsKnight, and what can you do for me?". It calls whoami and answers with your role, teams and enabled tools.
  3. In OpsKnight, select Check connection on the Connect tab to see the connection you just made.

Known limits

  • Request timeout defaults to 600,000 ms (timeout).
  • includeTools / excludeTools narrow the tool list (exclude wins). Tool names over 63 characters are truncated; OpsKnight's are shorter.
  • No tool-count or result-size cap is documented. OpsKnight lists at most 54 tools.
  • Avoid underscores in the server name: Gemini CLI's policy parser splits on them.

Troubleshooting

  • /mcp list (or gemini mcp list) shows the state; /mcp auth lists servers that need a sign-in.
  • Start with gemini --debug, or press F12 for the debug console.
  • An untrusted project folder disables its servers; run gemini trust there.

Last updated for v2.2.0

Edit this page on GitHub