Use TGlider with OpenCode

┌ ┐

└ ┘

│

┌ ┐

OpenCode Setup

Configure TGlider with OpenCode.

OpenCode

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

Create opencode.json in your project root. This local command setup uses stdio. OpenCode config files are merged, and project config overrides global defaults. OpenCode MCP docs: opencode.ai/docs/mcp-servers.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tglider": {
      "type": "local",
      "command": ["npx", "-y", "tglider"],
      "enabled": true
    }
  }
}

If you prefer Streamable HTTP, start TGlider yourself and configure OpenCode as a remote MCP server at http://localhost:5002/mcp.

npm exec -- tglider --transport http --port 5002

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tglider": {
      "type": "remote",
      "url": "http://localhost:5002/mcp",
      "enabled": true
    }
  }
}

Start a new OpenCode 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.

└ ┘