Glider
Roslyn-powered C# code analysis server for LLMs. Supports stdio and HTTP transports.
Runs on your machine from its package; the steps are below.
What it does
- Reads
- Writes
- High impact
At most: creates or changes data: records, files, settings.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Published to NuGet as `glider` — run it with your .NET MCP host.
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
| Product and installation | What it does |
|---|---|
| Glider | C#/.NET navigation, diagnostics, analysis, edits, and refactors |
| TGlider | TypeScript and JavaScript navigation, analysis, and edits |
| Scout | Repository search across files, text, code patterns, and concepts |
| JGlider preview | Read-only Java source and compiler evidence |
| Keep alpha | Shared local documents and project knowledge |
| GliderTrace | Command execution, tests, and .NET runtime evidence |
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
claude plugin marketplace add glidermcp/glidermcp
claude plugin install glidermcp@glidermcp
Codex CLI
codex plugin marketplace add glidermcp/glidermcp
codex plugin add glidermcp@glidermcp
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.
