Use GliderMCP with Claude Code for C# projects

✈ GliderMCP v6.12.0

┌ ┐

└ ┘

│

┌ ┐

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 --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 GliderMCP plugin bundles the C# workflow skill and stdio MCP config with a 30 minute async-tool timeout.

/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 only one glider server entry unless you intentionally want separate stdio and HTTP configs.

# 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?"

└ ┘