Glider MCP

Glider is a Roslyn-powered Model Context Protocol (MCP) server for semantic C# code analysis and refactoring in MCP clients (for example, Claude Code).

For full documentation and setup guides, see glidermcp.com.

What you can do with Glider

• Resolve symbols the same way the compiler does (not grep).
• Resolve ambiguous names into stable keys (symbolKey) and use them across tool calls.
• Find references, overrides, implementations, unused symbols, and unused parameters.
• Query symbols by semantic predicates and search solution text (literal/regex).
• Navigate type hierarchies, call graphs, direct impact, and cascade impact.
• Inspect APIs with detailed type information and method signatures.
• Surface compiler diagnostics and grouped hotspots for a loaded solution/project.
• Investigate NuGet packages and external assembly usage before cleanup work.
• Review project graphs and identify likely-unused direct project references.
• Refactor safely: rename symbols and move types/members with reference updates.
• Apply deterministic formatting with preview diffs.
• Analyze architecture via dependency and complexity metrics.
• Batch multiple tool calls into a single request.

Tool overview

• Diagnostics: server_status, get_diagnostics, diagnostic_hotspots
• Solution management: load, reload, sync, get_file_contents, write_file
• Symbol discovery: resolve_symbol, search_symbols, get_symbol_at_position, get_symbol_info
• References & relationships: find_unused_symbols, find_unused_parameters, find_references, find_overrides, find_implementations
• Code analysis: get_type_info, get_method_signature, get_type_source, get_method_source
• Semantic & text search: semantic_query, search_text
• Type hierarchy: get_type_hierarchy, get_derived_types, find_member_in_hierarchy
• Call graph & impact: find_callers, get_outgoing_calls, analyze_change_impact, get_cascade_impact
• Refactoring: rename_symbol, move_type, move_member
• Formatting: organize_usings, format_document
• External source & dependency usage: view_external_definition, find_external_dependency_usages, find_package_usages
• Architecture & metrics: get_type_dependencies, get_project_graph, find_unused_project_references, analyze_complexity
• Batching: batch

Installation

Prerequisites

• .NET 10 SDK

Install / update / uninstall

Prerequisite: Glider currently requires .NET 10 SDK to be installed.

Run dotnet --version before installing. If dotnet is missing or the installed SDK is below 10, install the .NET 10 SDK first. On Windows you can use winget install -e --id Microsoft.DotNet.SDK.10; on macOS/Linux use the official Microsoft .NET 10 installation guide: https://dotnet.microsoft.com/download/dotnet/10.0

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

Running Glider

Glider supports two transports:

• Stdio (default): for local MCP clients like Claude Code
• HTTP: for MCP clients that connect over Streamable HTTP

# Stdio (default)
glider

# Show CLI help and exit
glider --help
glider -h

# Print version and exit
glider --version
glider -v

# Enable logs and (for stdio) a startup banner on stderr
glider --verbose

# Change the default async-tool timeout
glider --default-timeout 30m

# HTTP (default port: 5001)
glider --transport http
# Listens on http://localhost:5001/mcp

glider --transport http --port 8080
# Listens on http://localhost:8080/mcp

glider --transport http --port 8080 --default-timeout 30m
# Listens on http://localhost:8080/mcp with a longer server-side timeout

Using with Claude Code (stdio)

# Project-scoped config (recommended)
claude mcp add --transport stdio glider --scope project -- glider

# For larger solutions
claude mcp add --transport stdio glider --scope project -- glider --default-timeout 30m

If

... View full README on GitHub