Install Glider

Choose your client and operating system. Follow the three stages below to connect one local workspace.

Operating system

1. Install

Requires .NET 10 SDK. Run this in your terminal. The command installs the executable on your machine.

dotnet tool install --global glider

Then confirm that the executable starts:

glider --version

Future packages will expire 90 days after release. Existing versions retain their original expiry. Keep the installed product updated. Update instructions →

2. Connect

Project directory

Use the absolute path to your project directory. The server stays tied to this workspace.

Solution or project file

Use a .sln, .slnx, or .csproj path relative to the project directory, or an absolute path.

Paths stay in this page. They are not saved or sent to analytics.

Example configuration. Enter your project path before you use it.

Merge this entry into the file below. Keep existing settings and other servers. Replace an existing entry with this name instead of duplicating it.

.vscode/mcp.json

{
  "servers": {
    "glider": {
      "type": "stdio",
      "command": "glider",
      "args": [
        "--solution",
        "/path/to/MyApp/src/App.slnx",
        "--workspace",
        "/path/to/MyApp",
        "--default-timeout",
        "30m"
      ],
      "cwd": "/path/to/MyApp"
    }
  }
}

VS Code uses a servers map, not mcpServers.

3. Verify

Open the project in VS Code. Run MCP: List Servers, start this server, and use Agent mode.

Ask your agent

Use Glider to check server_status. Wait until my selected solution or project is ready. Then find one symbol and its definition in that workspace. Do not edit files.

The status names your solution or project. The symbol result points to a file in it.

Agent instructions →