Glider
Give your coding agent Roslyn-accurate C# semantics, symbols, and refactor context without leaving the editor.
Overview
Glider is a MCP server for the Build phase that exposes Roslyn-powered C# code analysis to LLMs over stdio or HTTP.
What is this MCP server?
- Roslyn-powered C# analysis exposed as MCP tools for LLM agents
- stdio transport via NuGet package glider (registry install)
- HTTP transport option for remote or shared agent setups
- Targets LLM workflows that need compiler-grade C# understanding
- Server version 6.4.2
- NuGet package identifier glider with stdio transport
- Supports stdio and HTTP transports per server description
Community signal: 15 GitHub stars.
What problem does it solve?
Agents guessing at C# structure from raw files miss symbols, partial classes, and project graph edges that break refactors.
Who is it for?
Solo builders on .NET who want MCP-connected agents with real Roslyn semantics during backend implementation.
Skip if: Teams on non-C# stacks or builders who only need generic linting without a .NET toolchain.
What do I get? / Deliverables
After you register Glider, your agent can query compiler-backed C# analysis while you implement or change .NET backend code.
- MCP-connected Roslyn C# analysis during agent sessions
- stdio or HTTP transport wiring documented in server metadata
- Compiler-grade symbol and project context for agent prompts
Recommended MCP Servers
Journey fit
How it compares
Roslyn-backed MCP integration for C#, not a generic multi-language agent skill.
Common Questions / FAQ
Who is Glider for?
Glider is for indie developers and agent users working in C# who need MCP-accessible, compiler-grade code intelligence.
When should I use Glider?
Use Glider in the Build phase when your agent must navigate, analyze, or refactor .NET backend code with Roslyn accuracy.
How do I add Glider to my agent?
Install the glider NuGet MCP package for stdio or point your MCP client at the server’s HTTP endpoint per the glidermcp.com repository docs.