Configure Glider with any MCP-compatible client.
Prerequisite: .NET 10 SDK must be installed before running dotnet tool install --global glider.
When possible, configure Glider per project/workspace (not globally). This avoids launching it for unrelated projects (and can reduce token usage).
Most clients can run glider directly if your .NET tools directory is on PATH.
# bash/zsh
export PATH="$PATH:$HOME/.dotnet/tools"
which gliderMany clients (Cursor, Gemini CLI, Pi, etc.) use this format. Replace the file location with your client’s recommended project/workspace config file.
{
"mcpServers": {
"glider": {
"command": "glider",
"args": ["--default-timeout", "30m"]
}
}
}VS Code uses a different config format (see VS Code docs: code.visualstudio.com/docs/copilot/customization/mcp-servers).
{
"servers": {
"glider": {
"type": "stdio",
"command": "glider",
"args": ["--default-timeout", "30m"]
}
}
}If your client requires HTTP, start Glider in HTTP mode and point the client at http://localhost:5001/mcp. This example raises the async-tool timeout to 30 minutes; --default-timeout also accepts values like 45s or 0:
# Start Glider in HTTP mode
glider --transport http --default-timeout 30m
# Then configure your client to connect to:
# http://localhost:5001/mcpFor clients that accept a URL in mcpServers, use this shape after starting Glider in HTTP mode.
{
"mcpServers": {
"glider": {
"url": "http://localhost:5001/mcp"
}
}
}For VS Code and GitHub Copilot Chat, use type: "http" and the same local endpoint.
{
"servers": {
"glider": {
"type": "http",
"url": "http://localhost:5001/mcp"
}
}
}# Custom port and timeout for HTTP transport
glider --transport http --port 8080 --default-timeout 30m