A
licenseNot graded
qualityB
maintenanceLocal-first MCP server that persists AI coding agent memory and session context, enabling seamless resume across sessions with searchable memories and checkpoints.
7 npm
1
MIT
local-memo
Related Servers
Alternatives to local-memo
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA local MCP server that enables AI agents to securely read, write, search, and edit JSON and Markdown files through a gated permission-scoped interface with configurable access modes.MIT
- AlicenseBqualityDmaintenanceMCP server providing context usage estimation, conversation compaction, and durable semantic memory via local embeddings and SQLite.177 npm3MIT
- AlicenseAqualityAmaintenanceMCP Server that enables LLMs to interact with the local filesystem.131,923 npm20MIT
- AlicenseAqualityCmaintenanceProvides local persistent working memory for AI agents, allowing them to load rules, preferences, and project state before tasks and save validated experiences after successful completion. Works with stdio MCP clients via a local JSON file.5MIT
- AlicenseAqualityAmaintenancePersistent project context (AGENTS.md), cross-session memory, and identity — discoverable by any MCP client.491,040 npm2MIT
TDQS
A4.3/5.0
Scored across 4 tools
Disambiguation5/5
Each tool targets a distinct operation on memos: get retrieves, list enumerates, set saves, delete removes. There is no overlap or ambiguity between them.
Naming Consistency5/5
All tools follow the consistent pattern memo_<verb> (get, list, set, delete). The naming is uniform and predictable.
Tool Count5/5
Four tools is a well-scoped count for a simple memo/context storage service. Each tool is necessary and none are redundant.
Completeness5/5
The tool surface covers the full lifecycle of memos: create (set), read (get), list, and delete. No obvious missing operations for the stated purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues