Install Glider

Choose your client and operating system. Follow the three stages below to connect one local workspace.

Operating system

1. Prepare

Requires .NET 10 SDK. Run this in your terminal. The launcher downloads and caches the latest stable package. A global installation is optional.

dotnet tool exec "glider@*" --no-http-cache --verbosity quiet -- --version

The configuration below checks for the latest stable package at each server start. Restart the server to use an update.

Future packages will expire 90 days after release. Existing versions retain their original expiry. Keep the installed product updated. Update instructions →

2. Connect

Project directory

Use the absolute path to your project directory. The server stays tied to this workspace.

Solution or project file

Recommended: preload your .sln, .slnx, or .csproj with this configuration. Use a path relative to the project directory, or an absolute path.

Paths stay in this page. They are not saved or sent to analytics.

Example configuration. Enter your project path before you use it.

Run this from your project root. It adds a project-scoped server without replacing other entries.

.mcp.json

claude mcp add-json --scope project glider '{"type":"stdio","command":"dotnet","args":["tool","exec","glider@*","--no-http-cache","--verbosity","quiet","--","--solution","/path/to/MyApp/src/App.slnx","--workspace","/path/to/MyApp","--default-timeout","30m"],"timeout":1800000}'

This setup uses project scope. Keep the server entry in .mcp.json at your project root.

3. Verify

Restart Claude Code from your project root. Open /mcp and approve the project server when prompted.

Ask your agent

Use Glider to check server_status. Wait until my selected solution or project is ready. Then find one symbol and its definition in that workspace. Do not edit files.

The status names your solution or project. The symbol result points to a file in it.