Use TGlider with Gemini CLI

┌ ┐

└ ┘

│

┌ ┐

Gemini CLI Setup

Configure TGlider with Google Gemini CLI.

Gemini CLI

TGlider runs on Node.js 24 or newer. The recommended stdio configuration uses npx -y tglider, so a separate global install is optional.

node --version

Configure Gemini CLI to launch TGlider over stdio. Prefer project/workspace scope when the client supports it so TGlider only starts for JS/TS repositories.

{
  "mcpServers": {
    "tglider": {
      "command": "npx",
      "args": ["-y", "tglider"]
    }
  }
}

If you prefer Streamable HTTP, start TGlider yourself and point Gemini CLI at http://localhost:5002/mcp. Use only one tglider entry unless you intentionally want both transports.

# Terminal 1
npm exec -- tglider --transport http --port 5002

# Client endpoint
http://localhost:5002/mcp

Start a new client session and ask which TGlider tools are available. Load a JS/TS workspace with load before using semantic tools.

After connecting TGlider, add this product-specific instruction to your MCP client system prompt or project instructions so the agent chooses the right tool surface first.

When working in TypeScript or JavaScript workspaces, prefer tglider mcp semantic tools before grep, rg, or find for code navigation and refactoring. Use TGlider for symbols, declarations, references, implementations, exports, package importers, project and dependency topology, diagnostics, callers, outgoing calls, impact analysis, and preview-first rename or refactor planning. Use shell text search only for non-code assets, files outside the loaded workspace, generated output, or after TGlider cannot load or cannot answer the question.

└ ┘