whatisgithub

What is lexa?

anvia-hq/lexa — explained in plain English

Analysis updated 2026-05-18

83RustAudience · developerComplexity · 2/5LicenseSetup · easy

In one sentence

A local tool that scans your codebase and builds a searchable graph of it, so both you and AI coding assistants can look up functions, files, and dependencies consistently.

Mindmap

mindmap
  root((Lexa))
    What it does
      Indexes a codebase
      Builds a queryable graph
      Traces dependencies
    Tech stack
      Rust
      MCP protocol
      CLI
    Use cases
      Search code by text
      Look up symbols
      Connect AI assistant
    Audience
      Developers
      AI coding tools

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Search a large codebase for where a function or piece of text is used.

USE CASE 2

Get an outline of a file's contents without opening it.

USE CASE 3

Give an AI coding assistant a consistent view of your project via MCP.

USE CASE 4

Trace how different parts of the code depend on each other before making a change.

What is it built with?

RustMCPCLI

How does it compare?

anvia-hq/lexarun-llama/sandboxed-litjohunsang/semble_rs
Stars838386
LanguageRustRustRust
Setup difficultyeasymoderateeasy
Complexity2/53/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

So what is it?

Lexa is a command-line tool that analyzes a codebase and builds an internal graph representing how all the pieces connect. Once indexed, you can query that graph to search for text, look up specific functions or symbols, see an outline of a file's contents, or trace how different parts of the code depend on each other. The core idea is that both developers and AI coding assistants often need to understand a project's structure before making changes. Lexa provides a stable, shared view of the codebase so that any tool reading from it sees the same consistent picture rather than re-analyzing files independently. The tool runs entirely on your local machine, meaning no code is sent to external servers. It can be used from the command line directly, from within a code editor, or through a protocol called MCP (Model Context Protocol), which is how AI coding assistants can connect to it and use it as a source of information about your project. Installation is a single command for Mac and Linux, or a PowerShell one-liner for Windows. After that, running lexa index in your project folder processes the codebase, and the other commands let you query it. The README is brief and points to a separate documentation site for full details. The project is written in the Rust programming language and is licensed under the MIT open-source license.

Copy-paste prompts

Prompt 1
Install lexa and run 'lexa index .' on my project, then explain what the graph shows me.
Prompt 2
Set up lexa's MCP server so my AI coding assistant can query my project's structure.
Prompt 3
Use lexa to find every place that calls a specific function in my codebase.
Prompt 4
Show me how to get a file outline with lexa before I refactor it.

Frequently asked questions

What is lexa?

A local tool that scans your codebase and builds a searchable graph of it, so both you and AI coding assistants can look up functions, files, and dependencies consistently.

What language is lexa written in?

Mainly Rust. The stack also includes Rust, MCP, CLI.

What license does lexa use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is lexa to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is lexa for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.