
Glider
io.github.glidermcpPublished by GitHub account glidermcpv6.4.2Updated Oct 24, 2026
Roslyn-powered C# code analysis server for LLMs. Supports stdio and HTTP transports.
Overview
Glider is a local Roslyn-powered MCP server that lets an AI assistant navigate, analyze, edit and refactor C#/.NET code.
- What you can do
- Navigate C#/.NET code: find symbols and explore project structure through Roslyn analysis (tool list not published).
- When to use it
- Useful when a coding agent needs to work on C#/.NET solutions and should understand, edit or refactor code with compiler-backed analysis rather than plain text search.
- Requirements
- Runs as a local stdio process installed from NuGet. The Glider plugin requires the .NET 10 SDK and NuGet access, and selects the latest stable package at each server start. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Glider in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
GliderMCP
Local tools for coding agents. Start with Glider to navigate, analyze, edit, and refactor C#/.NET code through MCP.
Website · Documentation · Report a problem
Choose a product
Each product connects independently to your MCP client. Choose its installation guide for requirements, connection instructions, and verification.
Plugins and skills
This repository provides plugins for Claude Code and Codex:
- Glider plugin
- TGlider plugin
- Scout plugin
- JGlider preview plugin
- Keep skill-only plugin
- GliderTrace plugin
We recommend the skill for each product you use. Server plugins bundle skills with their MCP connection.
The Keep plugin supplies only a skill; connect one shared Keep HTTP server separately.
Glider and GliderTrace plugins require the .NET 10 SDK and NuGet access. They select the latest stable package at each server start.
TGlider and Scout plugins use npx with @latest; a global installation is optional.
JGlider uses npx -y --ignore-scripts jglider@next and requires Node.js 24+ and JDK 21+.
TGlider requires Node.js 24+; Scout requires Node.js 18+ and npm optional dependencies. TGlider does not require Scout.
For a new Glider connection, install its plugin with your chosen client:
Claude Code
Codex CLI
Start a new Codex session after installation. See the Codex plugin guide for details.
For another product, replace the plugin name before @ with tglider, scout, glider-trace, jglider, or keep.
Restart the MCP server to select an updated .NET package. A running process keeps its current version. For Glider, we recommend project preload with an explicit solution path.
For an existing manual MCP connection, install only the skill to keep your configuration. Use the migration instructions to replace an older global .NET launcher. Choose one connection per product; remove or disable a manual entry before enabling its server plugin. Keep is the exception: retain your existing HTTP connection because its skill-only plugin registers no server.
For substantial Claude Code tasks, use the bundled C# specialist and runtime verifier. The TypeScript specialist and Java specialist provide the same focused workflow. These agents give the work explicit product guidance. Small tasks can use the skills directly.
Price and privacy
The products will always be free for non-commercial use. Commercial use is free for now. Future packages will expire 90 days after release. Existing packages retain their embedded expiry date. Update before expiry. See pricing and license terms.
Servers process code locally. Your MCP client controls what returned content reaches its model provider. See privacy and telemetry for product data policies and controls.
Support and contributions
Open an issue and select the affected product or website. Documentation corrections, configuration fixes, and feature requests are welcome. See contribution guidance.
This repository contains public support resources, plugins, and configuration templates. It does not contain the product server implementations. Its MIT license covers this repository's assets. Product packages have their own license terms.
Source: README.md at commit 094a7e6
Tools
0Version history
1- v6.4.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts