Getting Started

Get Glaux file intelligence into your AI coding agent in under a minute. No install, no API keys — just connect to the cloud MCP server.

Prerequisites

Your repository must be seeded before Glaux tools return useful data. Showcase repos (tobi/qmd, transformerlab/transformerlab-app) are already seeded and ready to use. For your own repo, request it here — we'll seed it and keep it updated for free.

Connect your agent

Claude Code

One command:

claude mcp add glaux --transport http https://glaux.dev/api/mcp

Cursor

Add to .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "glaux": {
      "url": "https://glaux.dev/api/mcp"
    }
  }
}

Windsurf

Add to your MCP configuration:

{
  "mcpServers": {
    "glaux": {
      "serverUrl": "https://glaux.dev/api/mcp"
    }
  }
}

Any MCP-compatible agent

Point your agent's MCP config at:

https://glaux.dev/api/mcp

The transport is HTTP — no local process, no dependencies. Your agent connects directly to the Glaux cloud.

What your agent gets

Once connected to a seeded repo, the agent can:

• Check co-change patterns before editing files
• Flag high-churn or highly connected files
• Surface linked open issues
• Suggest related files that may need updating
• Assess blast radius before writing a line

See MCP Tools for the full tool reference.

Alternative: REST API

If your tooling doesn't support MCP, use the REST API directly. All showcase repos are publicly accessible — no auth required.

# Get file intelligence
curl https://glaux.dev/api/repos/tobi/qmd/file/src/llm.ts

# Get PR context
curl https://glaux.dev/api/repos/tobi/qmd/pr/10

# Get repo overview
curl https://glaux.dev/api/repos/tobi/qmd

What gets indexed?

Glaux analyzes your repository to compute:

• Churn metrics — commit count, additions/deletions, recent activity
• Co-change patterns — files that historically change together
• Importance & connectedness — which files are central in the co-change network
• Cluster detection — file groups identified via Leiden algorithm
• Momentum — whether co-change coupling is increasing, decreasing, or stable
• Issue links — GitHub issues and PRs linked to each file