Configure Glider with OpenCode.
dotnet tool install --global glider.dotnet tool install --global gliderglider is available on PATH.# bash/zsh
export PATH="$PATH:$HOME/.dotnet/tools"
which glideropencode.json in your project root. This local command setup uses stdio. OpenCode config files are merged, and project config overrides global defaults. OpenCode MCP docs: thdxr.dev.opencode.ai/docs/mcp-servers.{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"glider": {
"type": "local",
"command": ["glider", "--default-timeout", "30m"],
"enabled": true
}
}
}mcp block to ~/.config/opencode/opencode.json if you want Glider available across projects.{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"glider": {
"type": "local",
"command": ["glider", "--default-timeout", "30m"],
"enabled": true
}
}
}http://localhost:5001/mcp.glider --transport http --default-timeout 30m
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"glider": {
"type": "remote",
"url": "http://localhost:5001/mcp",
"enabled": true
}
}
}opencode mcp list
opencode
# Ask: "Use glider to load this solution and run server_status."When working in C#/.NET workspaces, prefer glider mcp semantic tools before shell text search for code navigation and refactoring. Use GliderMCP for symbol lookup, references, implementations, overrides, callers, call graphs, type and project dependencies, diagnostics, impact analysis, and preview-first refactors. Use grep, rg, or find only for non-C# assets, files outside the loaded workspace, generated output, or after GliderMCP cannot load or cannot answer the question.