
lien
by getlien
Lien
/ljɛ̃/, French for "link"
A code-intelligence layer for AI agents: structural analysis + fast lexical search. 100% local, 100% private.
Lien connects AI coding assistants like Cursor and Claude Code to your codebase through the Model Context Protocol (MCP). Its core value is structural: reverse dependencies and blast radius, complexity hotspots, and test associations, the questions an agent needs to answer before it edits your code. Alongside that, it offers fast lexical code search (FTS5/BM25 over code, docstrings, and identifier-split symbol names). Everything runs locally, with no embedding model to download: it installs in seconds and indexes offline.
Full Documentation | Getting Started | How It Works
Features
- Impact Analysis - Find all dependents and blast radius before refactoring, with risk assessment
- Complexity Analysis - Human-friendly metrics: test paths, mental load, time to understand
- Test Associations - Know which tests cover a file before you touch it
- Lexical Search - Fast full-text (FTS5/BM25) keyword search over code, docstrings, and identifier-split symbol names
- 100% Local & Private - All analysis happens on your machine
- No Model Download - No embeddings, no ~100MB model: tiny install, instant offline indexing
- MCP Integration - Works with Cursor, Claude Code, and other MCP-compatible tools
- Fast - Sub-millisecond file context; minutes to index large codebases
- Free Forever - No API costs, no subscriptions, no usage limits (applies to the local MCP/search tooling; Lien Review's agent pass uses your own LLM key and has its own token cost)
- Ecosystem-Aware & Monorepo - Auto-detects 12 ecosystem presets; supports 15+ languages
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 hooks are now available in every Claude Code session, in every repo, including a hook that enhances Claude Code's built-in Explore agent with Lien-tool guidance. First use in a new git repo triggers a one-time index automatically, with no lien init per project required.
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.
MCP Tools
Lien exposes 6 tools via Model Context Protocol:
| Tool | Description |
|---|---|
search_code | Full-text (BM25) keyword code search |
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 human-friendly 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 (Effort^(2/3) / 3000)
Lien Review
Lien Review is a self-hostable GitHub Action that reviews pull requests: complexity analysis, agent-driven bug review, and a PR summary, posted back as inline comments and workflow annotations. It runs without a server, a database, or a recurring bill.
# .github/workflows/lien
Related servers

n8n
by n8n-io
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.

@modelcontextprotocol/server-everything
OfficialMCP server that exercises all the features of the MCP protocol

@modelcontextprotocol/server-filesystem
OfficialMCP server for filesystem access