Use Glider with Claude Code for C# projects

Claude Code Setup

Configure Glider with Claude Code CLI.

Claude Code

Prerequisite: .NET 10 SDK must be installed before running dotnet tool install --global glider.

dotnet tool install --global glider

Most MCP clients can run glider directly if your .NET tools directory is on PATH. If you prefer, you can also use the full path to the executable (shown below).

# bash/zsh
export PATH="$PATH:$HOME/.dotnet/tools"
which glider

Use stdio for local Glider setup. Project-scoped servers only run when you are in that project. See Claude Code MCP docs: code.claude.com/docs/en/mcp.

claude mcp add --transport stdio glider --scope project -- glider --solution src/App.slnx --default-timeout 30m

Global config runs in every Claude Code project. Use this only if you want Glider available everywhere.

claude mcp add --transport stdio glider --scope user -- glider --default-timeout 30m

The Glider plugin is published from glidermcp/glidermcp.com and bundles the product skill plus stdio MCP config.

/plugin marketplace add glidermcp/glidermcp.com
/plugin install glidermcp@glidermcp

If you prefer Streamable HTTP, start Glider yourself and point Claude Code at http://localhost:5001/mcp. Use one glider server entry per workspace — to work on several solutions at once, add multiple named entries with different --solution values (see the FAQ).

# Terminal 1
glider --transport http --default-timeout 30m

# Terminal 2
claude mcp add --transport http --scope project glider http://localhost:5001/mcp

Start a new Claude Code session and check for Glider tools. If you need startup output/logs, re-add Glider with --verbose (e.g. ... -- glider --verbose).

claude
# Then ask: "What Glider tools are available?"

Add --solution <path> to the launch arguments in the configuration above so Glider loads your solution or project (a .sln, .slnx, or .csproj file) at startup, instead of waiting for the agent to call load. With it set, server_status shows the workspace as loaded — or, on a large workspace, still loading in the background under workspaceLoading — from the first message, so the agent can wait for that load to finish instead of stopping with a "No solution loaded. Use load first." message and reaching for text search. Put the flag after -- for claude mcp add, add it to the args array in JSON and Codex TOML configs, or to the single command array for OpenCode. For worktrees, prefer a relative path and launch the server from the selected worktree root. Relative paths use the server launch directory, not the config file directory. An absolute path intentionally pins one checkout.

# From the selected worktree root; replace src/App.slnx with your solution path.
glider --solution src/App.slnx --default-timeout 30m
# Add --workspace <dir> to watch a different root, or --no-watch to disable file watching.

Use a project-local config: Claude Code .mcp.json, Codex .codex/config.toml (trusted projects), Cursor .cursor/mcp.json, or VS Code .vscode/mcp.json. Include portable config files in version control, or copy local config files into each worktree. Git does not copy ignored files. Use absolute paths only when you intentionally want one fixed checkout, such as a global Claude Desktop configuration.

Open the client at the selected worktree root. Relative server arguments use the server launch directory, not the config file directory. Project scope alone does not guarantee that directory. If the client starts elsewhere, configure its MCP working directory or use a Git-root launcher.

Run git rev-parse --show-toplevel in the client terminal, then ask server_status for the server workspace. Confirm that the loaded solution or workspace belongs to that worktree before you query or change code. For a wrong root, explicitly load the intended workspace or restart the server with the correct path.

An existing HTTP server keeps its own workspace when the client changes directories. Use separate servers and ports for simultaneous worktrees.

git rev-parse --show-toplevel

Use this alternative when the client starts inside the worktree but below its root. It requires Git and a POSIX shell. Replace the existing server entry; do not add a second instance. For Glider, replace src/App.slnx with your solution path. On Windows, use the relative configuration above and set the MCP launch directory to the worktree root. This launcher cannot identify your worktree if the client starts outside its directory tree.

{
  "mcpServers": {
    "glider": {
      "command": "sh",
      "args": [
        "-c",
        "repo_root=$(git rev-parse --show-toplevel) && exec glider --solution \"$repo_root/src/App.slnx\" --default-timeout 30m"
      ]
    }
  }
}

After connecting Glider, add this product-specific instruction to your MCP client system prompt or project instructions so the agent chooses the right tool surface first.

When working in C#/.NET workspaces, prefer glider mcp semantic tools for symbol identity, code relationships, diagnostics, dependencies, impact analysis, and preview-first refactors. Use Scout for repository retrieval and raw text questions. Use the .NET CLI for build and test commands. Preload the solution with --solution, or call load before semantic queries.