LocalKeep MCP Server
Related Servers
Alternatives to LocalKeep MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLong-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.2151 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables 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.-
- FlicenseAqualityDmaintenanceEnables 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.9-
- AlicenseNot gradedqualityAmaintenanceGives an AI assistant a private, local memory of every past conversation, automatically surfacing relevant earlier exchanges and providing tools to search, read, browse a calendar of, and forget them.MIT

Nowledge Memofficial
AlicenseNot gradedqualityCmaintenanceEnables 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 remember conversations and learn over time by storing and recalling messages, memory abstracts, and recent history using a local SQLite database.422 npm71MIT
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.