Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Local semantic code search with Git history. Works offline, no API key needed.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CODE_MEMORY_LOG_LEVEL, EMBEDDING_MODELYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"code-memory": {
"command": "uvx",
"args": [
"code-memory"
],
"env": {
"CODE_MEMORY_LOG_LEVEL": "your-value",
"EMBEDDING_MODEL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add code-memory --env CODE_MEMORY_LOG_LEVEL=your-value --env EMBEDDING_MODEL=your-value -- uvx code-memoryFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"code-memory": {
"command": "uvx",
"args": [
"code-memory"
],
"env": {
"CODE_MEMORY_LOG_LEVEL": "your-value",
"EMBEDDING_MODEL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"code-memory": {
"type": "stdio",
"command": "uvx",
"args": [
"code-memory"
],
"env": {
"CODE_MEMORY_LOG_LEVEL": "your-value",
"EMBEDDING_MODEL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
CODE_MEMORY_LOG_LEVEL envEMBEDDING_MODEL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account kapillamba4, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.33) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A deterministic, high-precision code intelligence layer exposed as a Model Context Protocol (MCP) server.
uvx code-memory and you're readyPlease help star code-memory if you like this project!
Finding the right context from a large codebase is expensive, inaccurate, and limited by context windows. Dumping files into prompts wastes tokens, and LLMs lose track of the actual task as context fills up.
Instead of manually hunting with grep/find or dumping raw file text, code-memory runs semantic searches against a locally indexed codebase. Inspired by claude-context, but designed from the ground up for large-scale local search.
Full AST Support (structural parsing with symbol extraction): Python, JavaScript/TypeScript, Java, Go, Rust, C/C++, Ruby, Kotlin
Fallback Support (whole-file indexing): C#, Swift, Scala, Lua, Shell, Config (yaml/toml/json), Web (html/css), SQL, Markdown
Files matching
.gitignorepatterns are automatically skipped.
Instead of a single monolithic search, code-memory routes queries through three purpose-built tools:
| Question Type | Tool | Data Source |
|---|---|---|
| "Where / What / How?" — find definitions, references, structure, semantic search | search_code | BM25 + Dense Vector (SQLite vec) |
| "Architecture / Patterns" — understand architecture, explain workflows | search_docs | Semantic / Fuzzy |
| "Who / Why?" — debug regressions, understand intent | search_history | Git + BM25 + Dense Vector (SQLite vec) |
| "Setup / Prepare" — index parsing & embedding generation | index_codebase | AST Parser + sentence-transformers |
This forces the LLM to pick the *right retrieval strategy* before any data is fetched.
# Install with pip
pip install code-memory
uvx code-memory
# Clone the repo
git clone https://github.com/kapillamba4/code-memory.git cd code-memory
uv sync
uv run mcp run code_memory/server.py
Download standalone executables from GitHub Releases — no Python installation required.
| Platform | Architecture | File |
|---|---|---|
| Linux | x86_64 | code-memory-linux-x86_64 |
| macOS | x86_64 (Intel) | code-memory-macos-x86_64 |
| macOS | ARM64 (Apple Silicon) | code-memory-macos-arm64 |
| Windows | x86_64 | code-memory-windows-x86_64.exe |
# Linux/macOS: Download and make executable
chmod +x code-memory-* ./code-memory-*
code-memory-windows-x86_64.exe
Note: The first run will download the embedding model (~600MB) to ~/.cache/huggingface/. Subsequent runs use the cached model.
uv package manager (recommended) or pipInstall uv if you don't have it:
curl -LsSf https://astral.sh/uv/install.sh | sh
# Install from PyPI
pip install code-memory
uvx code-memory
# Run with the MCP Inspector for interactive debugging
uv run mcp dev code_memory/server.py
uv run pytest tests/ -v
uv run ruff check . uv run ruff format .
uv build
pip install pyinstaller pyinstaller --clean code-memory.spec
You can use either uvx (requires Python) or the standalone binary (no dependencies).
Add to your MCP settings (e.g. ~/.gemini/settings.json):
{
"mcpServers": { "code-memory": { "command": "uvx", "args": ["code-memory"] } } }
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": { "code-memory": { "command": "uvx", "args": ["code-memory"] } } }
Add to .mcp.json in your project root or ~/.mcp.json for global access:
{
"mcpServers": { "code-memory": { "command": "uvx", "args": ["code-memory"] } } }
Add to .vscode/mcp.json in your workspace:
{
"servers": { "code-memory": { "command": "uvx", "args": ["code-memory"] } } }
Replace the path with the location of your downloaded binary:
{
"mcpServers": { "code-memory": { "command": "/path/to/code-memory-linux-x86_64" } } }
For Windows:
{
"mcpServers": { "code-memory": { "command": "C:\\path\\to\\code-memory-windows-x86_64.exe" } } }
By default, each MCP host project launches its own code-memory process, which loads the embedding model (~1–2 GB) once per project. To avoid this, you can run a single shared instance over SSE (Server-Sent Events) and point all your MCP hosts at it.
# Using uvx (recommended)
uvx code-memory --transport sse
uvx code-memory --transport sse --port 8765 --host 127.0.0.1
./code-memory-linux-x86_64 --transport sse
The server listens on http://127.0.0.1:8765/sse by default.
Instead of launching a new process, point your MCP host at the running SSE endpoint.
{
"mcpServers": { "code-memory": { "url": "http://127.0.0.1:8765/sse" } } }
{
"servers": { "code-memory": { "url": "http://127.0.0.1:8765/sse" } } }
.mcp.json{
"mcpServers": { "code-memory": { "url": "http://127.0.0.1:8765/sse" } } }
Tip: Configure
uvx code-memory --transport sseto start via a single-instance service manager (e.g. systemd user service, launchd agent, or another one-time login/startup mechanism) so the shared server starts automatically.
Security: The SSE endpoint is unauthenticated. Keep the default
--host 127.0.0.1so only local processes can connect; do not bind to0.0.0.0or a public interface unless you've put authentication in front of it.
| Option | Description | Default |
|---|---|---|
--transport | Transport protocol: stdio or sse | stdio |
--port | Port for SSE transport (only when --transport sse is used) | 8765 |
--host | Host/bind address for SSE transport (only when --transport sse is used) | 127.0.0.1 |
| Variable | Description | Default |
|---|---|---|
CODE_MEMORY_LOG_LEVEL | Logging verbosity (DEBUG, INFO, WARNING, ERROR) | INFO |
EMBEDDING_MODEL | HuggingFace model ID for embeddings | jinaai/jina-code-embeddings-0.5b |
Example:
CODE_MEMORY_LOG_LEVEL=DEBUG uvx code-memory
You can use a different embedding model by setting the EMBEDDING_MODEL environment variable:
EMBEDDING_MODEL="BAAI/bge-small-en-v1.5" uvx code-memory
For MCP hosts, add the environment variable to your configuration:
{
"mcpServers": { "code-memory": { "command": "uvx", "args": ["code-memory"], "env": { "EMBEDDING_MODEL": "BAAI/bge-small-en-v1.5" } } } }
Note: Changing the embedding model will invalidate existing indexes. You'll need to re-run
index_codebaseafter switching models.
index_codebaseIndexes or re-indexes source files and documentation in the given directory. Run this before using search_code or search_docs to ensure the database is up to date. Uses tree-sitter for language-agnostic structural extraction and generates dense vector embeddings using sentence-transformers (runs locally, in-process) for semantic search.
index_codebase(directory=".")
search_codePerform semantic search and find structural code definitions, locate where functions/classes are defined, or map out dependency references (call graphs). Uses hybrid retrieval (BM25 + vector embeddings) to find exact matches and semantic similarities.
search_code(query="parse python files", search_type="definition")
search_code(query="how do we establish the database connection", search_type="references") search_code(query="src/auth/", search_type="file_structure")
search_docsUnderstand the codebase conceptually — how things work, architectural patterns, SOPs. Searches markdown documentation, READMEs, and docstrings extracted from code.
search_docs(query="how does the authentication flow work?")
search_docs(query="installation instructions", top_k=5)
search_historyDebug regressions and understand developer intent through Git history.
search_history(query="fix login timeout", search_type="commits")
search_history(query="src/auth/login.py", search_type="file_history", target_file="src/auth/login.py") search_history(query="server.py", search_type="blame", target_file="server.py", line_start=1, line_end=20)
code-memory/
├── code_memory/ # Package source │ ├── server.py # MCP server entry point (FastMCP) │ ├── db.py # SQLite database layer with sqlite-vec │ ├── parser.py # Tree-sitter-based code parser │ ├── doc_parser.py # Markdown documentation parser │ ├── queries.py # Hybrid retrieval query layer │ ├── git_search.py # Git history search module │ ├── errors.py # Custom exception hierarchy │ ├── validation.py # Input validation functions │ ├── logging_config.py # Structured logging configuration │ └── api_types.py # MCP response TypedDicts ├── tests/ # Test suite ├── pyproject.toml # Project metadata & dependencies └── prompts/ # Milestone prompt engineering files
Make sure you're running search_history from within a git repository. The tool searches upward from the current directory to find .git.
Run index_codebase(directory=".") first to index your code and documentation. The index is stored locally in code_memory.db.
Indexing generates embeddings using a local sentence-transformers model. The first run downloads the model (~600MB for jina-code-embeddings-0.5b). Subsequent runs are faster.
Ensure you have enough disk space and memory. The jina-code-embeddings-0.5b model requires ~1GB RAM when loaded.
**Your code never leaves your
Only the beginning is shown; read the rest in the repo