Use GliderMCP with GitHub Copilot and VS Code

GliderMCP

┌ ┐

└ ┘

│

┌ ┐

GitHub Copilot Setup

Configure Glider with GitHub Copilot Chat (VS Code).

GitHub Copilot

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

dotnet tool install --global glider

VS Code launches stdio MCP servers via command. Make sure glider is available on PATH.

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

Create .vscode/mcp.json in your repo. VS Code MCP docs: code.visualstudio.com/docs/copilot/customization/mcp-servers.

{
  "servers": {
    "glider": {
      "type": "stdio",
      "command": "glider",
      "args": ["--default-timeout", "30m"]
    }
  }
}

If you prefer Streamable HTTP, start Glider yourself and configure VS Code with http://localhost:5001/mcp.

glider --transport http --default-timeout 30m

{
  "servers": {
    "glider": {
      "type": "http",
      "url": "http://localhost:5001/mcp"
    }
  }
}

Reload the window to apply changes. If you prefer global setup, configure MCP servers in your VS Code user settings (see GitHub docs above).

After connecting GliderMCP, 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 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.

└ ┘