What is GliderMCP?

GliderMCP is a local MCP server that helps coding agents navigate, analyze, and refactor C#/.NET codebases using semantic code information instead of plain text search.

Why not just use grep or ripgrep?

Grep finds matching text. GliderMCP finds code relationships: real definitions, references, implementations, overrides, callers, diagnostics, and change impact.

Why not just rely on the LLM?

The LLM does not automatically know your local codebase. Without tools, it guesses from opened files and search results. GliderMCP gives it structured facts about the loaded solution.

Does my code leave my machine?

No prompts, code, or customer data are sent to GliderMCP servers. The MCP server runs locally and analyzes files in your workspace.

Which clients work with GliderMCP?

Any MCP-compatible client. The install docs include setup guides for Claude Code, Cursor, GitHub Copilot, Codex, Gemini CLI, OpenCode, Pi, and generic MCP clients. See Compatibility for client and transport details.

Does it support .NET Framework?

Yes, as long as the project or solution can be loaded and analyzed successfully with your local .NET/MSBuild tools. Windows with a stable Visual Studio/MSBuild installation is the most reliable setup for legacy .NET Framework solutions. See Compatibility for the full matrix.

Can it change files?

Yes, for supported refactoring and file-write workflows. Prefer preview-first changes where available, especially when editing shared code.

What do I need to install GliderMCP?

You need the .NET 10 SDK installed locally and an MCP-compatible client.

Run dotnet --version before installing. If dotnet tool install succeeds but glider is not found, confirm that your .NET tools directory is on PATH.

Can I use HTTP transport?

Yes. Run glider --transport http --default-timeout 30m to start a Streamable HTTP MCP server at http://localhost:5001/mcp. This is useful for clients that connect over HTTP.