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 chronological memory banks you control; Claude recalls them via MCP.
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.
LOCALKEEP_DATA_DIR, LOCALKEEP_DB_PATHYou 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": {
"localkeep": {
"command": "uvx",
"args": [
"localkeep"
],
"env": {
"LOCALKEEP_DATA_DIR": "your-value",
"LOCALKEEP_DB_PATH": "your-value"
}
}
}
}Run this in your terminal
claude mcp add localkeep --env LOCALKEEP_DATA_DIR=your-value --env LOCALKEEP_DB_PATH=your-value -- uvx localkeepFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"localkeep": {
"command": "uvx",
"args": [
"localkeep"
],
"env": {
"LOCALKEEP_DATA_DIR": "your-value",
"LOCALKEEP_DB_PATH": "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": {
"localkeep": {
"type": "stdio",
"command": "uvx",
"args": [
"localkeep"
],
"env": {
"LOCALKEEP_DATA_DIR": "your-value",
"LOCALKEEP_DB_PATH": "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.
LOCALKEEP_DATA_DIR envLOCALKEEP_DB_PATH 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 zuneracodes, 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.3) reached the registry 3 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.
LocalKeep is for anyone who wants a chronological memory layer for chatbots where *they* directly control *what* the model remembers about them. Instead of forcing you to rely on a black-box cloud memory that the model invents around you that you can't even edit, LocalKeep lets you curate titled, dated, editable memory banks directly on your own machine where you write the entries and manage them locally via a localhost Hub UI. When a conversation requires your prior context, Claude queries your local data through a secure, native Model Context Protocol (MCP) connector.
AI Chat apps are great at *sounding* like they remember you, but struggle at recalling the exact thing you care about — *what* happened, on *which* date, about *whom*? Consumer memory features tend to lack the capacity for true temporal reasoning, flattening your history into a soft, generic vibe summary instead of understanding that Event A triggered Event B three months ago, causing its reasoning to fail when you need something specific: a life event, a research arc, a decision you logged months ago. Worse yet, consumer AI memory is a black box: you don't get to decide what the model chooses to remember about you, how it interprets your life, or when it invents context around you.
LocalKeep fixes both structural flaws at once by replacing fragile, model-invented timelines with a rigid, chronological source of your truth, all while giving *you* absolute editorial control. You decide exactly *what* the AI is allowed to know about you. You write the entries, you anchor the dates, and you keep them local on your own machine. Claude simply acts as the lookup engine via MCP when a conversation requires your prior context. LocalKeep bridges the gap between structured personal logging and intelligent AI retrieval, ensuring your context is curated by you—not hallucinated by an LLM.
Who it’s for
What it is (and isn’t)
The Hub UI intentionally adopts a retro, Windows 95/MS Paint-inspired homage with customizable features to ensure LocalKeep feels like a deeply personal tool rather than an impersonal, rigid dashboard. By putting adjustable interface elements right at your fingertips, the UI signals that you are entering an intimate, offline workshop for your mind—a space you can shape and reconfigure to feel entirely like your own.
pip install localkeep
Then:
localkeep-hub # http://127.0.0.1:8000
In Claude Desktop, register the MCP server (claude_desktop_config.json):
{
"mcpServers": { "localkeep": { "command": "localkeep-mcp", "args": [] } } }
If the GUI can’t find localkeep-mcp on your PATH, use the absolute path from which localkeep-mcp (the Hub’s Connect panel copies this for you).
Memories default to ~/.localkeep/localkeep.db when installed via pip. Override with LOCALKEEP_DATA_DIR or LOCALKEEP_DB_PATH.
Claude will not reliably call MCP tools unless you also set Personal preferences:
src/localkeep/assets/claude-personal-preferences.txt)git clone https://github.com/zuneracodes/localkeep
cd localkeep uv sync --group dev uv run localkeep-hub # http://127.0.0.1:8000
LOCALKEEP_HUB_RELOAD=1 uv run localkeep-hub
From a source checkout, the DB lives in data/localkeep.db (gitignored).
These smoke-check the Hub, retrieval, and MCP tools so a fresh install still stores and recalls dated memories the way a real user would.
uv sync --group dev
uv run pytest
Tests start from an empty DB and create memories through Hub form POSTs (same path as a new user).
Storage is local. Banks and memories live in your chosen DB path (~/.localkeep/ for pip installs, or data/localkeep.db in a checkout). There is no LocalKeep cloud and nothing is auto-scraped from chat. Theme colors stay in browser localStorage. Refreshing the Hub page or restarting localkeep-hub does not delete your banks — only removing the database file does.
Recall goes through Claude. The Hub and database stay on your machine, but when Claude calls a LocalKeep MCP tool, the matching memories are returned into that chat and Anthropic processes them like any other tool result. LocalKeep isn’t shipping your whole DB upstream — only what that lookup returns for the question at hand.
Bug reports and pull requests are welcome via GitHub Issues. Please run uv run pytest before opening a PR.
MIT — see LICENSE.