Glider MCP v6.6.1
┌ ┐
└ ┘
│
┌ ┐

Quick Start

Get Glider MCP running in minutes.

Prerequisites

Run dotnet --version before installing Glider. If dotnet is missing or the installed SDK is below 10, install the .NET 10 SDK first.

Windows: winget install -e --id Microsoft.DotNet.SDK.10. macOS/Linux: use the official Microsoft .NET 10 installation guide.

  • .NET 10 SDK
  • An MCP-compatible AI client (Claude Code, Cursor, etc.)

1. Install Glider

dotnet tool install --global glider

2. Verify Installation

# List installed tools
dotnet tool list -g

# The tool path should be in your PATH
# macOS/Linux: ~/.dotnet/tools
# Windows: %USERPROFILE%\.dotnet\tools

3. Configure Your AI Client

See the Installation section for client-specific instructions.

4. Start Using

Once configured, you can ask your AI assistant:

"Load the solution at /path/to/MySolution.sln"
"Load the solution at /path/to/MySolution.slnx"
"Load the solution at /path/to/MySolution.sln with file watching in /path/to/workspace"
"Load /path/to/MySolution.sln, run diagnostic_hotspots, and show the biggest compiler hotspot"
"Use search_symbols with query *Service and kinds Type to find all service classes"
"Find likely-unused private symbols and summarize the top cleanup candidates"
"Get the project graph and identify direct project references that may be removable"
"Find package usages for System.Text.Json and summarize the impacted files"
"What methods does IUserRepository define?"
"Resolve the Login method and then find_references for the selected symbolKey"
"I changed some files on disk. Sync the documents to see the latest changes."

Notes

In stdio mode, glider waits for MCP input and is intentionally quiet by default. Use glider --verbose if you want startup output/logs (written to stderr).

Async tools use a 20 minute server-side default timeout. Increase it with glider --default-timeout 30m, or use 0 to disable it. Supported units: ms, s, and m.

Update to Latest

dotnet tool update --global glider
└ ┘