LocalKeep
About
You decide what Claude remembers about you. LocalKeep is a personal timeline you curate—titled, dated, editable banks on your machine—then Claude looks them up via MCP instead of inventing uneditable cloud memory.
Details
- Author
- zuneracodes
- Categories
- AI, Other
Jump to
Setup
Install LocalKeep in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/zuneracodes/localkeep
Follow the installation instructions in the repository README, then restart your MCP client.
LocalKeep is for anyone who wants a chronological memory layer for chatbots wheretheydirectly controlwhatthe 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 atsoundinglike they remember you, but struggle at recalling theexactthing you care about —whathappened, onwhichdate, aboutwhom? 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 decidewhatthe model chooses to remember about you,howit interprets your life, orwhenit invents context around you.
LocalKeepfixes both structural flaws at once by replacing fragile, model-invented timelines with a rigid, chronological source ofyourtruth, all while givingyouabsolute editorial control. You decide exactlywhatthe 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 byyou—not hallucinated by an LLM.
- Anyone frustrated that chat memory can’t reliably fetch dated facts or understand timelines
- People who already maintain meticulous personal diaries, work logs, or research archives. Instead of settling for a generic chat-app paraphrase, you get to inject yourexactwords and historical data into the prompt as an unyielding source of truth.
- Users who trust Claude for its reasoning capability, but demand that their foundational context database remains stored locally under their own roof. (Note: Querying memories via MCP still sends theretrieved text fragmentsto Anthropic during the session).
- Is:A lightweight customizable local Hub UI to manage your dated memory banks, paired with an MCP server that Claude Desktop can call.
- Isn’t:A standalone chat application, a cloud-hosted memory API, or a background utility that silently scrapes your personal conversations.
The Hub UI intentionally adopts a retro, Windows 95/MS Paint-inspired homage with customizable features to ensure LocalKeep feels like a deeplypersonal toolrather 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 # or: uv tool install localkeep
In Claude Desktop, register the MCP server (claude_desktop_config.json):
{ "mcpServers": { "localkeep": { "command": "localkeep-mcp", "args": [] } } }
If the GUI can’t findlocalkeep-mcpon yourPATH, use the absolute path fromwhich localkeep-mcp(the Hub’s Connect panel copies this for you).
Memories default to~/.localkeep/localkeep.dbwhen installed via pip. Override withLOCALKEEP_DATA_DIRorLOCALKEEP_DB_PATH.
Claude will not reliably call MCP tools unless you also setPersonal preferences:
- Claude Desktop →Settings→Profile→Personal preferences
- Paste the LocalKeep instructions (Hub → Connect →Copy instructions, or seesrc/localkeep/assets/claude-personal-preferences.txt)
- Quit Claude completelyand reopen
- When LocalKeep asks to run a tool, clickAlways approve
git clone https://github.com/zuneracodes/localkeep cd localkeep uv sync --group dev uv run localkeep-hub # http://127.0.0.1:8000 # optional live reload: LOCALKEEP_HUB_RELOAD=1 uv run localkeep-hub
From a source checkout, the DB lives indata/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.
Tests start from anempty DBand 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, ordata/localkeep.dbin a checkout). There is no LocalKeep cloud and nothing is auto-scraped from chat. Theme colors stay in browserlocalStorage. Refreshing the Hub page or restartinglocalkeep-hubdoesnotdelete 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 viaGitHub Issues. Please runuv run pytestbefore opening a PR.
Atlaso is a memory layer for AI tools — connect once and it automatically recalls the context that matters across Claude Code, Cursor, Codex, and every AI tool you use.
Privacy-first local memory vault every AI shares over MCP. Markdown + SQLite on your machine; Claude, ChatGPT, Cursor, and any MCP client read and write it live. No cloud, no account, no telemetry.
Cross-vendor AI memory over MCP. One semantic memory store, readable and writeable from every MCP client — Claude, ChatGPT, Cursor, Windsurf, Zed, Kimi.
Generate random word pairs for the Imposter party game directly via Claude or Cursor. Let AI host your next social deduction game!
Shared company context and governed tools for ChatGPT, Claude, Codex and other MCP clients.
Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.
Persistent project context for AI coding agents: captures decisions, rationale, and rejected paths so agents stay consistent across Claude, Cursor, Codex, and any MCP enabled platform.
Private persistent memory for Claude, ChatGPT & Gemini via MCP — semantic search, zero-code setup.
Turn LinkedIn saved posts into a queryable knowledge base you can search, chat with, and connect to Claude or ChatGPT through MCP.
Cross-tool proactive memory + suggestions for Claude Code, Kimi Code, Cline, Cursor. Teach once, use everywhere.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.




