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)
Persistent session memory for Claude Code. Local SQLite, no LLMs, no network.
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.
You 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": {
"memex": {
"command": "uvx",
"args": [
"mcp-memex"
]
}
}
}Run this in your terminal
claude mcp add memex -- uvx mcp-memexPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"memex": {
"command": "uvx",
"args": [
"mcp-memex"
]
}
}
}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": {
"memex": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-memex"
]
}
}
}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.
These 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 8, 2026
The registry name was verified with the GitHub account pragneshbagary, 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 (0.1.9) reached the registry 5 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.
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