Install GliderTrace

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

Operating system

1. Prepare

Requires .NET 10 SDK. Run this in your terminal. The launcher downloads and caches the latest stable package. A global installation is optional.

dotnet tool exec "glider-trace@*" --no-http-cache --verbosity quiet -- --version

The configuration below checks for the latest stable package at each server start. Restart the server to use an update.

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.

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

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

Run this from your project root. It adds a project-scoped server without replacing other entries.

.mcp.json

claude mcp add-json --scope project glider-trace '{"type":"stdio","command":"dotnet","args":["tool","exec","glider-trace@*","--no-http-cache","--verbosity","quiet","--","--workspace","/path/to/MyApp","--default-timeout","30m"],"timeout":1800000}'

This setup uses project scope. Keep the server entry in .mcp.json at your project root.

3. Verify

Restart Claude Code from your project root. Open /mcp and approve the project server when prompted.

Ask your agent

Use GliderTrace trace_status to show the workspace roots and runner policies. Confirm that my project is the intended workspace. Do not execute a command yet.

The status includes your workspace and the available runner policies. Run a test only when you choose the next task.