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. Install Glider:

dotnet tool install --global glider

Choose your MCP client for connection instructions and a verification step.

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.

Example: check the callers after an edit

Ask your agent:

Find CalculateTotal and its callers. Preview a change from decimal to decimal?. Apply the reviewed change. Check the callers.

The agent can read the file and preview the change with write_file and applyChanges: false:

- public decimal CalculateTotal() => 42m;
+ public decimal? CalculateTotal() => 42m;

After application, get_diagnostics identifies a caller that still assigns the result to a non-nullable value:

decimal total = service.CalculateTotal(); // CS0266

The caller must handle a null result. We verified this illustrative example with Glider 11.0.0.

Choose the right edit

A semantic rename updates symbol references. A source replacement changes the selected code; it does not adapt callers to a new signature.

Preview support and defaults differ by tool. write_file writes by default; set applyChanges: false to inspect its diff first. Read the edit-tool reference for availability, source guards, diagnostic scope, and recovery after a failed workspace update.

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 glider --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, retry with glider --build-host netframework. 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. Use glider --verbose 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 one month after release. Update Glider:

dotnet tool update --global glider

Restart your MCP client after the update.

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. The send_feedback tool can publish a public issue. See privacy and controls.

Report a problem. Read the documentation.