Use Glider with OpenCode

OpenCode Setup

Configure Glider with OpenCode.

OpenCode

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

dotnet tool install --global glider

OpenCode launches local MCP servers through a command array. Make sure glider is available on PATH.

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

Create opencode.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
    }
  }
}

Add the same 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
    }
  }
}

If you prefer Streamable HTTP, start Glider yourself and configure OpenCode as a remote MCP server at 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
    }
  }
}

List configured MCP servers, then start OpenCode and ask it to use Glider for a C# workspace.

opencode mcp list
opencode
# Ask: "Use glider to load this solution and run server_status."

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. Prefer an absolute path — it is machine-specific, so keep it in local or user scope — or a relative path (resolved against the launch directory) when the config is shared in a project.

glider --solution C:/repos/app/src/App.sln --default-timeout 30m
# Add --workspace C:/repos/app to watch a different root, or --no-watch to disable file watching.

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.