Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Persistent session memory for Claude Code. Local SQLite, no LLMs, no network.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"memex": {
"command": "uvx",
"args": [
"mcp-memex"
]
}
}
}在终端中运行这条命令
claude mcp add memex -- uvx mcp-memex粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"memex": {
"command": "uvx",
"args": [
"mcp-memex"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"memex": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-memex"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 pragneshbagary 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.9)于5个月前进入注册中心。
支持 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、图片和脚本已被移除。链接会离开本站。
Every Claude Code session starts without knowing what you built last time - which files you changed, what decisions you made, what broke. You re-explain. Claude re-reads. You start over.
memex keeps a structured log of every session. Claude reads it at the start of the next one.
No cloud. No LLM extraction. No cost per save. Just local SQLite and one command to install.
# with uv
uvx mcp-memex install
pip install mcp-memex memex install
Restart Claude Code. That's it.
Each entry has structure - not a blob of text:
mem_save(
task="Replaced JWT auth with session cookies", files=["src/auth.py", "src/middleware.py"], decisions=["Session cookies over JWT - simpler, no token refresh needed"], warnings=["Redis required - app won't start without REDIS_URL set"], tags=["auth", "sessions"] )
Claude calls mem_save when it finishes something meaningful. You can also just tell it: *"save what we just did."*
=== memex: session context (db: my_project.db) ===
--- Recent (2) --- [1] #4 - 2026-06-14T10:32 Task : Replaced JWT auth with session cookies Files : src/auth.py, src/middleware.py Decision : Session cookies over JWT - simpler, no token refresh needed Warning : Redis required - app won't start without REDIS_URL set Tags : auth, sessions
[2] #3 - 2026-06-13T15:10 Task : Added rate limiting to /api/login Files : src/middleware.py Warning : Rate limiter is in-memory per process - resets on restart Tags : auth, rate-limiting
Claude calls mem_load automatically at the start of every session. It returns the most recent entries plus any entries that match what you're working on - by keyword and by file path.
You don't need to be inside Claude to look at your history:
memex status # entry count, DB size, top tags
memex list # recent entries for this project memex list --tag auth # filter by tag memex list --since 7d # entries from the last 7 days memex list --since 2026-06-01 --until 2026-06-15 # date range memex search "rate limit" # full-text search memex version # print installed version
Turn your history into portable, human-browsable notes - one .md file per entry, with [[wikilinks]] connecting related entries and files, plus tags as #hashtags. Works in Obsidian or any tool that understands [[links]]:
memex export ./my-project-notes/
Entries that share a tag or a touched file are cross-linked under a Related section, so you can navigate your project history as a graph.
| Tool | What it does |
|---|---|
mem_load | Called at session start - returns recent + relevant entries |
mem_save | Saves a structured entry after meaningful work |
mem_update | Patches specific fields of an existing entry (keeps id and timestamp) |
mem_search | Full-text search across all entries |
mem_list | Lists entries, optionally filtered by tag |
mem_delete | Removes a stale entry by id |
CLAUDE.md is for static project documentation - architecture, conventions, how to run tests. It doesn't change much and it isn't session-aware.
memex captures what's changing session to session: what you built yesterday, the decision you made this morning, the warning you discovered an hour ago. It's the difference between *"here's the project"* and *"here's what happened last time."*
memex install writes Claude's instructions into .claude/CLAUDE.local.md - a file Claude Code loads automatically without touching your project's own CLAUDE.md.
Each project gets its own SQLite database at ~/.memex/ .db based on the working directory. Sessions from different projects never mix.
Set these in the MCP env block in ~/.claude.json if you need to override defaults:
| Variable | Default | Description |
|---|---|---|
MEMEX_DIR | ~/.memex | Where DBs are stored |
MEMEX_GLOBAL | 0 | Set to 1 to share one DB across all projects |
MEMEX_RECENT | 5 | Max recent entries loaded per session |
MEMEX_MATCHED | 5 | Max FTS-matched entries loaded per session |
memex remove
pip uninstall mcp-memex
Memory DBs are kept at ~/.memex/ - delete that directory manually if you want to wipe everything.
mcp package (installed automatically)MIT