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. This avoids launching it for unrelated projects. Most clients read a project-scoped config file: Claude Code .mcp.json (claude mcp add --scope project), Cursor .cursor/mcp.json, VS Code / GitHub Copilot .vscode/mcp.json, Gemini CLI .gemini/settings.json, OpenCode opencode.json, and Pi .mcp.json. Claude Desktop only supports one global claude_desktop_config.json with no per-project scope, so pin a project there by adding --solution to its args, or use Claude Code for per-project setups.
Add this product-specific instruction to your MCP client system prompt or project instructions after connecting Glider.
When working in C#/.NET workspaces, prefer glider mcp semantic tools for symbol identity, code relationships, diagnostics, dependencies, impact analysis, and preview-first refactors. Use Scout for repository retrieval and raw text questions. Use the .NET CLI for build and test commands. Preload the solution with --solution, or call load before semantic queries.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 30mAdd --solution <path> to the launch arguments in the configuration above so Glider loads your solution or project (a .sln, .slnx, or .csproj file) at startup, instead of waiting for the agent to call load. With it set, server_status shows the workspace as loaded — or, on a large workspace, still loading in the background under workspaceLoading — from the first message, so the agent can wait for that load to finish instead of stopping with a "No solution loaded. Use load first." message and reaching for text search. Put the flag after -- for claude mcp add, add it to the args array in JSON and Codex TOML configs, or to the single command array for OpenCode. Prefer an absolute path — it is machine-specific, so keep it in local or user scope — or a relative path (resolved against the launch directory) when the config is shared in a project.
glider --solution C:/repos/app/src/App.sln --default-timeout 30m
# Add --workspace C:/repos/app to watch a different root, or --no-watch to disable file watching.