LocalKeep MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LocalKeep MCP Server What memories do I have from May 2024?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LocalKeep
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.
Why use LocalKeep
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
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 your exact words 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 the retrieved text fragments to Anthropic during the session).
What it is (and isn’t)
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.
Related MCP server: Fuzzy Memory MCP Server
The Aesthetic Philosophy
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.
Install
pip install localkeep
# or: uv tool install localkeepThen:
localkeep-hub # http://127.0.0.1:8000In 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.
Auto-use LocalKeep (important)
Claude will not reliably call MCP tools unless you also set Personal preferences:
Claude Desktop → Settings → Profile → Personal preferences
Paste the LocalKeep instructions (Hub → Connect → Copy instructions, or see
src/localkeep/assets/claude-personal-preferences.txt)Quit Claude completely and reopen
When LocalKeep asks to run a tool, click Always approve
Develop from source
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-hubFrom a source checkout, the DB lives in data/localkeep.db (gitignored).
Tests
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 pytestTests start from an empty DB and create memories through Hub form POSTs (same path as a new user).
Privacy
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.
Contributing
Bug reports and pull requests are welcome via GitHub Issues. Please run uv run pytest before opening a PR.
License
MIT — see LICENSE.
Available Tools
4 toolsget_bankGet memory bankARead-only
Load all memories from one bank by title (exact or partial match).
USE when a bank title matches the topic or person the user is asking about.
Inputs: bank_title (required). Returns: result
get_memories_by_date_rangeMemories by date rangeARead-only
Fetch memories whose event_date falls in a date range.
USE when the user mentions a month, year, or period, or asks what they were working on during a timeframe. Combine with query/entity for topic or person.
Inputs: date_to (required), date_from (required), limit, entity. Returns: result
list_banksList memory banksARead-only
List memory bank titles so you can pick the right timeline.
USE to discover which banks exist before get_bank or a targeted search.
Inputs: no named parameters. Returns: result
search_memoriesSearch personal memoriesARead-only
Search the user's curated memory banks (local Hub).
USE FIRST when context about the user's own past — personal OR work/research — would help answer the question.
Examples of triggers: a person from their past, picking up a research topic, continuing a report or project, any dated "what did I do then" question.
Pass query (keywords), entity (person or topic tag from memories), and/or date range. Returns titled, dated facts the user wrote — authoritative for their timeline.
Inputs: limit, query, entity, date_to, +2 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
search_memories and get_memories_by_date_range overlap significantly because search_memories already accepts a date range, making the dedicated date-range tool largely redundant. list_banks and get_bank are clearly distinct, but the two retrieval tools create ambiguity in tool selection.
All tools use clear lowercase snake_case verb_noun names. The pattern is consistent across search_memories, get_memories_by_date_range, list_banks, and get_bank, each following an imperative verb + object structure.
With only 4 tools, the server is tightly scoped for its purpose of querying memory banks. Each tool has a distinct role in discovery and retrieval, and there is no bloat.
The server covers the main retrieval needs: searching across banks, filtering by date, listing banks, and loading a full bank. However, there is no way to search within a specific bank without loading all its memories, and no single-memory fetch by ID, so some workflows require client-side filtering.
Related MCP Connectors
Your own memory inside ChatGPT and Claude, with the source of every note.
Portable AI memory you own. Keep memories and notes across Claude, ChatGPT, and other AI tools.
Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.
Persistent personal memory for AI assistants: search what you told it before and save new facts.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceEnables Claude to add and search personal memories through the Nowledge Mem service. Allows users to store and retrieve contextual information across conversations.4MIT- AlicenseAqualityDmaintenanceEnables Claude to maintain persistent memory across conversations using a local knowledge graph with fuzzy search capabilities, allowing it to remember and recall information about users, relationships, and context.9MIT
- AlicenseAqualityBmaintenanceLong-term memory for Claude Desktop and Claude Code over plain markdown files on your machine. It returns nothing when the corpus has no answer, naming the terms that appear nowhere — no least-bad match dressed as an answer. And it verifies cited commit SHAs against git, so an agent can tell what actually shipped from what was only discussed and abandoned. Local; nothing is transmitted.270 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables Claude to recall and query past conversations through a local knowledge graph and vector index, with tools for searching memory, retrieving related entities, and adding new memories.1-