Get started with Lumr

Five minutes from install to an AI agent querying your system graph instead of guessing at it.

Already have an account? Sign in →

Free forever. No credit card required. Terms of Service.

What Lumr understands about your codebase

Lumr parses your source files and infrastructure config, extracts every meaningful relationship, and stores it as a typed graph you can query from the CLI, the API, or an AI agent.

Files and packages

Every source file, workspace package, and npm dependency — with the imports and exports between them.

Functions, classes, interfaces

Sub-file declarations with call relationships, inheritance chains, and type references.

Infrastructure services

Docker Compose services, Kubernetes workloads, Terraform resources — linked to the packages that deploy them.

Supported languages and formats

TypeScriptJavaScriptDocker ComposeKubernetesTerraformPython — soonGo — soonJava / Kotlin — soon

For AI agents

Structural context, not hallucinated guesses

MCP server

lumr mcp exposes the system graph as MCP tools. Drop it into Claude, Cursor, Windsurf, or any MCP client. Agents get deterministic structural facts — not probabilistic guesses from file contents. Every response carries a coverage and freshness signal so agents know how much to trust what they're seeing.

Cross-repo reasoning

On paid plans, Lumr resolves imports across repositories. Your agent sees the full picture, not just the repo it's working in.

Grounded impact queries

Ask "what breaks if I change this?" and get a precise answer from the graph — not a guess from file contents.

No source code required

Lumr sends only the abstract graph to the cloud and to your agent. Source code never leaves your machine.

For engineers

Answer the questions that slow you down

Impact analysis

Before changing a file, know exactly which packages, services, and tests are affected — direct and transitive.

CI impact checks

lumr check reports the blast radius of any change — impacted packages, direct and transitive dependents — so you know the risk before merging. On TEAM+, it enforces configurable thresholds, failing the build when the impact exceeds what you've defined.

Dependency auditing

Find dead modules, circular dependencies, and unresolved imports. See which infrastructure services are linked to which packages.

Architecture visibility

Traverse the graph in any direction. Who calls this function? What does this service depend on? What deploys this package?

Set up in minutes

Install the CLI, authenticate, and ingest your first repo.

1

Create a free account

Use the button above to sign in or create an account. A Lumr account is all you need before installing the CLI.

2

Install the CLI

macOS — Homebrew

brew tap lumrapp/tap
brew install lumr

Linux / macOS — shell installer

curl --proto '=https' --tlsv1.2 -LsSf \
  https://github.com/lumrapp/lumr-cli/releases/latest/download/lumr-cli-installer.sh | sh
3

Authenticate

lumr auth login

Opens a browser window. If you already signed in on the web your session carries over — the token is issued and captured immediately without re-entering credentials.

4

Ingest a repository

cd /path/to/your/repo
lumr ingest .

Registers the repo with your workspace, extracts the graph, and stores it locally. On paid plans the graph also syncs to Lumr Cloud, enabling cross-repo queries and team sharing.

5

Connect an AI agent

optional

Add lumr mcp to your AI client to give it live structural context.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "lumr": {
      "command": "lumr",
      "args": ["mcp"],
      "cwd": "/path/to/your/repo"
    }
  }
}

Cursor, Windsurf, and other MCP clients use the same command, args, and cwd in their MCP settings panel.

Ready to understand your system?

Free forever. No credit card required.

Create free account