GliderMCP v6.11.2
┌ ┐
└ ┘
│
┌ ┐

Compatibility

GliderMCP works with C# solutions and projects that your local .NET/MSBuild tools can load.

The Glider tool itself requires the .NET 10 SDK. Project support depends on whether the installed SDKs, workloads, and build tools can evaluate and restore your solution or project.

Solution and Project Types

Load a solution or project with the load tool before using semantic navigation, diagnostics, or refactoring tools.

AreaCurrent supportNotes
.slnSupportedRecommended for multi-project solutions when the solution loads successfully with local .NET/MSBuild tools.
.slnxSupportedSupported when the solution loads successfully with local .NET/MSBuild tools.
.csprojSupportedUseful for focused single-project analysis or when a full solution is not available.
SDK-style C# projectsSupportedWorks for modern SDK-style projects when required SDKs and workloads are installed.
Legacy MSBuild C# projectsSupported with local build toolsGlider can analyze legacy projects when your local build tools can evaluate them.
Non-C# project systemsNot a Glider .NET targetGlider is the C#/.NET product. Use product-specific MCPs for other language ecosystems.

Target Frameworks

AreaCurrent supportNotes
Modern .NETSupportedIncludes current SDK-style .NET projects when matching SDKs and workloads are installed.
.NET CoreSupportedSupported when the project restores and loads with local .NET/MSBuild tools.
.NET StandardSupportedSupported for C# projects that can be loaded by the installed SDK/build toolchain.
.NET FrameworkSupported with caveatsMost reliable on Windows with a stable Visual Studio/MSBuild installation available to the local environment.

Operating Systems

AreaCurrent supportNotes
WindowsSupportedBest choice for legacy .NET Framework solutions that depend on Visual Studio or Windows-only build targets.
macOSSupportedWorks for SDK-style and other cross-platform C# projects when the required .NET SDKs and workloads are installed.
LinuxSupportedWorks for SDK-style and other cross-platform C# projects when the required .NET SDKs and workloads are installed.

MCP Clients and Transports

AreaCurrent supportNotes
Claude CodeSupportedUse the Claude Code setup guide for project or user scope.
Codex CLISupportedUse Codex setup with Streamable HTTP at http://localhost:5001/mcp.
Gemini CLISupportedUse the Gemini CLI setup guide with stdio MCP configuration.
CursorSupportedUse the Cursor setup guide with project or user MCP settings.
GitHub Copilot / VS CodeSupportedUse the Copilot setup guide for VS Code MCP configuration.
Other MCP-compatible clientsSupportedUse generic MCP configuration with stdio or Streamable HTTP.
Stdio transportDefaultStart Glider with glider unless your client requires another transport.
Streamable HTTP transportSupportedStart Glider with glider --transport http; default endpoint is http://localhost:5001/mcp.

Compatibility Notes

  • Glider reports load diagnostics from your local .NET/MSBuild tools. If a project cannot be evaluated locally, install the missing SDK, workload, targeting pack, or build tool and reload.
  • Support means Glider can load and analyze the solution or project through local tooling. It is not a guarantee that every custom target, generator, or design-time build dependency is available on every operating system.
  • For larger solutions, raise the server-side timeout with --default-timeout, for example glider --default-timeout 30m.
└ ┘