Lien
/ljɛ̃/ — French for "link"
Give AI deep understanding of your codebase through semantic search. 100% local, 100% private.
Lien connects AI coding assistants like Cursor and Claude Code to your codebase through the Model Context Protocol (MCP). Ask questions in natural language, get precise answers from semantic search—all running locally on your machine.
📚 Full Documentation | 🚀 Getting Started | 🔍 How It Works
Features
- 🔒 100% Local & Private - All code analysis happens on your machine
- 🚀 Semantic Search - Natural language queries: "How does authentication work?"
- 🌐 Cross-Repo Search - Search across all repositories in your organization (Qdrant backend)
- 🎯 MCP Integration - Works seamlessly with Cursor, Claude Code, and other MCP-compatible tools
- ⚡ Fast - Sub-500ms queries, minutes to index large codebases
- 🆓 Free Forever - No API costs, no subscriptions, no usage limits
- 📦 Framework-Aware - Auto-detects Node.js, Laravel, and more; supports 15+ languages
- 🏗️ Monorepo Support - Index multiple frameworks in one repository
- 📊 Complexity Analysis - Human-friendly metrics: test paths, mental load, time to understand
- 🔍 Impact Analysis - Find all dependents before refactoring with risk assessment
Quick Start
Claude Code (recommended) — one-time plugin install
/plugin marketplace add getlien/lien
/plugin install lien
That's it. Lien's MCP tools and the Explore agent are now available in every Claude Code session, in every repo. First use in a new git repo triggers a one-time index automatically — no lien init per project.
Other editors (Cursor, Windsurf, OpenCode, Kilo Code, Antigravity)
# 1. Install
npm install -g @liendev/lien
# 2. Wire it up for your editor
lien init
# 3. Restart your editor and start asking questions
lien init writes the right MCP config for your editor and (for Claude Code's legacy per-project flow, via lien init --legacy) copies an Explore agent into .claude/agents/. Lien auto-detects your project and indexes on first use.
👉 Full installation guide
Qdrant Backend (Cross-Repo Search)
For cross-repository search across your organization, configure Qdrant:
# Option 1: Global config file
mkdir -p ~/.lien
cat > ~/.lien/config.json <<EOF
{
"backend": "qdrant",
"qdrant": {
"url": "http://localhost:6333",
"apiKey": "your-api-key"
}
}
EOF
# Option 2: Environment variables
export LIEN_BACKEND=qdrant
export LIEN_QDRANT_URL=http://localhost:6333
export LIEN_QDRANT_API_KEY=your-api-key
# Index your repos (orgId auto-detected from git remote)
lien index
Note: orgId is automatically extracted from your git remote URL. Cross-repo search requires all repos to share the same orgId.
MCP Tools
Lien exposes 6 powerful tools via Model Context Protocol:
| Tool | Description |
|---|
semantic_search | Natural language code search (supports crossRepo with Qdrant) |
find_similar | Find similar code patterns |
get_files_context | Get file context with test associations |
list_functions | List symbols by pattern |
get_dependents | Impact analysis (what depends on this?) |
get_complexity | Tech debt analysis with human-friendly metrics |
Complexity Metrics
Lien tracks code complexity with intuitive outputs:
- 🔀 Test paths - Cyclomatic complexity as "needs ~X tests for full coverage"
- 🧠 Mental load - Cognitive complexity with nesting penalty
- ⏱️ Time to understand - Halstead effort as readable duration (~2h 30m)
- 🐛 Estimated bugs - Halstead prediction (Volume / 3000)
Documentation
Supported Languages
TypeScript • JavaScript • Vue • Python • PHP • Liquid • Go • Rust • Java • C/C++ • Ruby • Swift • Kotlin • C# • Scala • Markdown
Ecosystem Presets: 12 ecosystem presets including Node.js, Python, PHP, Laravel, Ruby, Rails, Rust, JVM, Swift, .NET, Django, and Astro (auto-detected)
Contributing
Contributions welcome! See CONTRIBUTING.md for guidelines.
Support
