Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Local semantic code search with Git history. Works offline, no API key needed.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
CODE_MEMORY_LOG_LEVEL, EMBEDDING_MODEL你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"code-memory": {
"command": "uvx",
"args": [
"code-memory"
],
"env": {
"CODE_MEMORY_LOG_LEVEL": "your-value",
"EMBEDDING_MODEL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add code-memory --env CODE_MEMORY_LOG_LEVEL=your-value --env EMBEDDING_MODEL=your-value -- uvx code-memory运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"code-memory": {
"command": "uvx",
"args": [
"code-memory"
],
"env": {
"CODE_MEMORY_LOG_LEVEL": "your-value",
"EMBEDDING_MODEL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"code-memory": {
"type": "stdio",
"command": "uvx",
"args": [
"code-memory"
],
"env": {
"CODE_MEMORY_LOG_LEVEL": "your-value",
"EMBEDDING_MODEL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
CODE_MEMORY_LOG_LEVEL envEMBEDDING_MODEL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 kapillamba4 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.0.33)于6个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
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.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
只显示了开头部分;其余内容请在仓库中阅读