LiLBrain
Correlate OpenTelemetry traces with static call graph for runtime correlation, identifying hot paths and dead code.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LiLBrainwhat functions call parse_request?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LiLBrain
Instant codebase knowledge graph MCP server.
Drop it into any project. It auto-detects languages, indexes every function, class, and call chain, then serves it all through MCP (Model Context Protocol) — so your LLM can navigate code in milliseconds instead of reading thousands of lines.
Why
Reading 5,000 lines to understand a call chain costs ~50K tokens. One graph query costs ~200 tokens. That's a 250x cost reduction.
LiLBrain turns any codebase into a queryable knowledge graph with zero configuration.
Related MCP server: Orihime
Supported Languages (20+)
Python, Rust, Go, TypeScript, JavaScript, Java, C, C++, C#, Ruby, PHP, Swift, Kotlin, Scala, Zig, Lua, Elixir, Dart, Vortex — plus aliases (.jsx, .tsx, .mjs, .hpp, .cc, .exs).
Install
pip install lilbrainOr clone:
git clone https://github.com/MangoByteLabs/LiLBrain.git
cd LiLBrain
pip install -e .Quick Start
As MCP Server (for Claude, etc.)
Add to your .mcp.json:
{
"mcpServers": {
"lilbrain": {
"command": "lilbrain",
"args": ["/path/to/your/project"]
}
}
}Or with Python directly:
{
"mcpServers": {
"lilbrain": {
"command": "python3",
"args": ["-m", "lilbrain", "/path/to/your/project"]
}
}
}CLI Mode
# Stats overview
lilbrain /path/to/project --stats
# Quick function lookup
lilbrain /path/to/project --query main
# Dump full graph JSON
lilbrain /path/to/project --dumpWhat It Indexes
Feature | Description |
Functions | Name, params, return type, location, docstring, complexity scores |
Classes | Structs, enums, traits, interfaces, modules |
Call Graph | Who calls whom — full caller/callee edges |
Subsystems | Auto-classified from directory structure |
Pipelines | Auto-detected from function naming patterns |
Constants | UPPER_CASE constants, typed consts, finals |
Cross-edges | Cross-subsystem dependency map |
Sections | Code sections marked with |
Complexity | Cyclomatic + cognitive complexity per function |
Semantic Index | TF-IDF vectors for meaning-based search |
MCP Tools (24)
Core Graph (12)
Tool | Description |
| Project summary: files, functions, languages, subsystems |
| Look up any function — signature, location, callers, callees |
| Full call graph for a function |
| Search everything: functions, classes, sections, constants |
| File info: functions, classes, sections, language |
| Read source code of a function or file region |
| Deep dive into a subsystem |
| Trace a pipeline (parse, validate, compile, etc.) |
| Upstream callers and downstream callees |
| Depth-limited call chain trace |
| Most connected functions (highest fan-in + fan-out) |
| Architecture map: subsystems and cross-dependencies |
Impact & Quality (4)
Tool | Description |
| Blast radius analysis — change a function, see everything affected |
| Find functions with zero callers + LOC waste estimate |
| Detect near-duplicate functions (token Jaccard similarity) |
| Auto-generate Mermaid or D2 architecture diagrams |
Intelligence (4)
Tool | Description |
| Cyclomatic + cognitive complexity ranking |
| Track complexity changes over git history |
| Semantic search — find functions by meaning, not name |
| Multi-repo federated search across codebases |
Tier 3 — AI-Native (4)
Tool | Description |
| Natural language questions — auto-routes to the right analysis |
| Git-aware graph diff: changed functions, blast radius, risk |
| Auto-generate PR review context with risk assessment |
| Correlate OpenTelemetry traces with static call graph |
Features
Impact Analysis
Change a function? LiLBrain tells you exactly what breaks:
lilbrain_impact("parse_request")
→ 47 functions affected across 5 subsystems
→ Risk: HIGH
→ Subsystems: api, auth, middleware, handlers, testsAuto Architecture Diagrams
Generate always-accurate Mermaid diagrams from live code:
lilbrain_diagram("architecture")
→ graph TD
api["api\n120 fns | 3400 LOC"]
auth["auth\n45 fns | 1200 LOC"]
api -->|12| authDead Code & Clone Detection
lilbrain_deadcode()
→ 847/3200 functions unreachable (26.5%)
→ 12,400 LOC wasted
lilbrain_clones()
→ adam_step <-> adamw_step (88.5% similar)
→ tcp_recv <-> udp_recv (83.3% similar)Semantic Search
Find functions by what they do, not what they're named:
lilbrain_semantic("handle user authentication")
→ verify_token (auth/jwt.py:45) score=14.2
→ check_session (middleware/session.rs:120) score=11.8
→ validate_credentials (api/login.go:33) score=9.4Natural Language Queries
lilbrain_ask("what is the most complex code?")
→ eval_stmt: cyclomatic=189, cognitive=198
→ lex: cyclomatic=171, cognitive=182
lilbrain_ask("show me dead code")
→ 847 functions with zero callers...
lilbrain_ask("who calls parse_request?")
→ handle_http, route_api, middleware_chain...Git Time-Travel & PR Review
lilbrain_diff("main", "feature-branch")
→ 12 files changed, 34 functions modified
→ Blast radius: 156 functions affected
→ Risk: HIGH
→ New cross-subsystem edge: api -> payments (didn't exist before!)
lilbrain_pr_review()
→ **8 files changed**, **23 functions modified**
→ **Blast radius**: 89 functions potentially affected
→ **Risk**: MEDIUM
→ **New cross-subsystem edges**: auth -> billing
→ **Complexity in changed code**: 45Multi-Repo Federation
Search across all your repos at once:
lilbrain_federation(query="authenticate", repos=["/app/api", "/app/auth", "/app/gateway"])
→ api: 3 matches
→ auth: 12 matches
→ gateway: 5 matchesRuntime Correlation
Connect static analysis to production reality:
lilbrain_runtime(trace_dir="traces/")
→ Hot paths: handle_request (45,000 calls, avg 2.3ms)
→ Cold code: legacy_handler (0 invocations — truly dead)Auto-Reindex
LiLBrain watches for file changes and a .graph-dirty sentinel file. Touch .graph-dirty in your project root (e.g., from a git post-commit hook) and the graph rebuilds automatically on the next query.
# Add to .git/hooks/post-commit:
touch .graph-dirtyPerformance
Project Size | Files | Functions | Index Time |
Small (1K LOC) | ~10 | ~40 | <0.1s |
Medium (50K LOC) | ~200 | ~2,000 | ~0.5s |
Large (360K LOC) | ~550 | ~16,800 | ~2.2s |
Zero dependencies. Pure Python 3.10+. Works everywhere.
How It Works
Walk — recursively finds all source files, skipping
node_modules,.git,__pycache__, etc.Detect — identifies language from file extension, loads the right regex patterns
Extract — pulls out functions, classes, sections, constants from each file
Connect — builds a call graph by scanning function bodies for known function names
Analyze — computes complexity scores, builds TF-IDF semantic index
Classify — auto-groups files into subsystems based on directory structure
Serve — exposes everything through 24 MCP tools over JSON-RPC stdin/stdout
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MangoByteLabs/LiLBrain'
If you have feedback or need assistance with the MCP directory API, please join our Discord server