glider

Glider

Navigate, analyze, edit, and refactor C#/.NET code with your coding agent. Glider provides compiler-backed tools through MCP and runs locally against your solution.

Install and connect

Install the .NET 10 SDK. Choose your MCP client for connection instructions and a verification step. The recommended configuration checks for the latest stable package at each server start. The launcher caches package files. A global installation is optional.

We recommend a project configuration that preloads your solution with --solution:

dotnet tool exec "glider@*" --no-http-cache --verbosity quiet -- --solution /path/to/App.sln

Replace the path with your .sln, .slnx, or .csproj. The agent waits for the selected workspace to load. The configuration generator creates the corresponding client entry.

Install the Glider skill for agent guidance. Follow the plugin or standalone skill instructions. Keep only one MCP connection per product. For substantial Claude Code tasks, use the bundled C# specialist described there.

What you can do

• Navigate: find declarations, references, implementations, and callers across projects.
• Analyze: inspect diagnostics, dependencies, complexity, and change impact.
• Edit and refactor: preview source edits, rename symbols, and move types or members.
• Clean up: identify likely-unused code and project references; format documents and organize imports.
• Inspect dependencies: trace package usage and read external definitions.

See example tasks or the tool reference.

Scope and setup

Glider analyzes loaded C# projects. Its search_text tool also searches their declared additional files and analyzer configuration files. Use Scout for files outside that scope.

Run dotnet tool exec "glider@*" --no-http-cache --verbosity quiet -- --help for CLI options. The setup guide covers automatic solution loads, workspaces, HTTP, and troubleshooting. Check compatibility for supported projects and platforms.

For a legacy .NET Framework build-host failure on Windows, add --build-host netframework to the server arguments after --. Use --msbuild-path "C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin" if Glider selects the wrong toolset. Replace that path with your installed MSBuild directory. Add --verbose to the server arguments for diagnostic details.

Updates and license

Glider will always be free for non-commercial use and work on open-source projects. Other commercial use is free for now. See the LICENSE file in this package for the full terms.

Each package expires 90 days after release. Restart the server to use the latest stable package with the recommended configuration. Other active agents can continue with their current version. See update options for network requirements, fixed versions, and SDK selection.

For a manual global installation:

dotnet tool install --global glider
dotnet tool update --global glider

Use glider as the client command for this alternative. Remove the launcher arguments from tool through the -- separator. Keep the server arguments that follow it. Stop servers that use the global installation before you update it. Restart them afterward.

Package expiry is separate from license duration.

Privacy and support

Glider processes code locally. Your MCP client controls what returned content reaches its model provider. Glider enables usage telemetry by default. Use --no-telemetry or DO_NOT_TRACK=1 to disable telemetry and agent feedback. Glider keeps sanitized records of unexpected product errors in ~/.glidermcp/diagnostics/ even when telemetry is off. While Glider runs, it removes inactive files older than 14 days. It allows 20 MiB for Glider and 5 MiB per file. Set GLIDER_LOCAL_ERROR_LOG=0 to disable these local records. This setting does not change telemetry or feedback. The send_feedback tool can publish a public issue. See privacy and controls.

Report a problem. Read the documentation.