Gemini CLI - Stackone

Overview

The Gemini CLI is Google’s open-source command-line agent. It connects to MCP servers defined in its settings.

Setup

StackOne’s MCP endpoint is a remote, Streamable HTTP server:

https://api.stackone.com/mcp

Get your MCP URL

In the StackOne dashboard, open a connector, click Use in Agent, select a linked account, and copy the generated token URL.

Add the server to Gemini

Add StackOne to ~/.gemini/settings.json under mcpServers:

{
  "mcpServers": {
    "stackone": {
      "httpUrl": "https://api.stackone.com/mcp?token={session_token}"
    }
  }
}

Or use the CLI: gemini mcp add --transport http stackone "https://api.stackone.com/mcp?token={session_token}".

Verify

Run gemini, then /mcp to list connected servers and their tools.

For API-key auth instead of a token URL, see Authentication & Security. Confirm the latest config format in the Gemini CLI MCP docs.

Handling large tool catalogs

If the connector exposes many actions, add the tool-mode=search_execute query parameter to the MCP URL in your config. The client then registers just two tools — search + execute — and the agent discovers actions at runtime, so the context footprint stays flat however large the catalog:

https://api.stackone.com/mcp?tool-mode=search_execute

For a token URL, append it as an extra parameter: https://api.stackone.com/mcp?token=<session_token>&tool-mode=search_execute. See Tool Discovery for how search works, its accuracy, and the other modes.

Optimize and secure

With your agent connected, use StackOne’s platform features to optimize performance and secure every call.

Search & Execute

Reduce context and save tokens.

Data Sync

Reduce latency and enable semantic search.

Defender

Block prompt injections before they reach your agent.

Flowise Goose CLI & Desktop

​Overview

​Setup

​Handling large tool catalogs

​Optimize and secure