Configure TGlider with any MCP-compatible client.
Install Node.js 24 or newer. The simplest stdio setup can run TGlider through npx -y tglider.
When possible, configure TGlider per project/workspace. This avoids starting it for repositories where JS/TS semantic tools are not useful.
Add this product-specific instruction to your MCP client system prompt or project instructions after connecting TGlider.
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.Many clients use this shape. Replace the file location with your client's recommended project or workspace config file.
{
"mcpServers": {
"tglider": {
"command": "npx",
"args": ["-y", "tglider"]
}
}
}VS Code uses a different server map shape. Use this for GitHub Copilot Chat or compatible VS Code MCP flows.
{
"servers": {
"tglider": {
"type": "stdio",
"command": "npx",
"args": ["-y", "tglider"]
}
}
}If your client requires HTTP, start TGlider in HTTP mode and point the client at http://localhost:5002/mcp. The /health endpoint is available on the same port.
# Start TGlider in HTTP mode
npm exec -- tglider --transport http --port 5002
# Then configure your client to connect to:
# http://localhost:5002/mcpFor clients that accept a URL in mcpServers, use this shape after starting TGlider in HTTP mode.
{
"mcpServers": {
"tglider": {
"url": "http://localhost:5002/mcp"
}
}
}For VS Code and GitHub Copilot Chat, use type: "http" and the same local endpoint.
{
"servers": {
"tglider": {
"type": "http",
"url": "http://localhost:5002/mcp"
}
}
}