Generic MCP Configuration

Configure Glider with any MCP-compatible client.

Prerequisite

Prerequisite: .NET 10 SDK must be installed before running dotnet tool install --global glider.

Recommendation: Project/Workspace Scope

When possible, configure Glider per project/workspace (not globally). This avoids launching it for unrelated projects (and can reduce token usage).

macOS / Windows / Linux: ensure glider is on PATH

Most clients can run glider directly if your .NET tools directory is on PATH.

# bash/zsh
export PATH="$PATH:$HOME/.dotnet/tools"
which glider

Stdio Transport (common: mcpServers JSON)

Many clients (Cursor, Gemini CLI, etc.) use this format. Replace the file location with your client’s recommended project/workspace config file. For larger solutions, set args to ["--default-timeout", "30m"].

{
  "mcpServers": {
    "glider": {
      "command": "glider",
      "args": []
    }
  }
}

VS Code / Copilot (mcp.json)

VS Code uses a different config format (see VS Code docs: code.visualstudio.com/docs/copilot/chat/mcp-servers). For larger solutions, set args to ["--default-timeout", "30m"].

{
  "servers": {
    "glider": {
      "type": "stdio",
      "command": "glider",
      "args": []
    }
  }
}

HTTP Transport

If your client requires HTTP, start Glider in HTTP mode and point the client at the URL. Async tools use a 20 minute server-side default timeout; change it with --default-timeout using values like 45s, 30m, or 0:

# Start Glider in HTTP mode
glider --transport http --default-timeout 30m

# Then configure your client to connect to:
# http://localhost:5001/mcp

Environment Variables

# Custom port and timeout for HTTP transport
glider --transport http --port 8080 --default-timeout 30m