C# / .NET semantic analysis

Glider

Semantic C# code navigation for LLM agents.

Glider gives MCP clients a compiler-backed map of C# code: definitions, references, implementations, call graphs, diagnostics, impact analysis, and preview-first refactoring.

Use it when an agent needs to understand a .NET codebase without reading files one by one or relying on text search for symbol identity.

Install

dotnet tool install --global glider

Agent Prompt Recommendation

After connecting the server, add a product-specific instruction to the MCP client system prompt so the agent reaches for semantic tools before falling back to raw CLI search.

System prompt snippet

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.

Requirements

.NET 10 SDK installed locally.
An MCP client that can launch stdio servers or connect to Streamable HTTP.
A C# solution or project that can be loaded by local .NET/MSBuild tooling.

Common Workflows

Find symbol definitions, references, implementations, overrides, and callers.
Inspect diagnostics and diagnostic hotspots before and after edits.
Preview symbol, type, and member refactorings before applying changes.
Map project and type dependencies for architecture and impact review.

Run Modes

Stdio: the default mode for MCP clients that launch Glider as a local process.
HTTP: run a local server when a client connects to Streamable HTTP at http://localhost:5001/mcp.

Update Policy

Each Glider release expires one month after its release date.

Update before or when the server reports that the local build is close to expiry.

dotnet tool update --global glider