agent-memory-router
Related Servers
Alternatives to agent-memory-router
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to persist and retrieve project-scoped memories across sessions using local SQLite FTS5 keyword search.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to persistently save, search, retrieve, update, link, and forget project-scoped memories through MCP tools, using local SQLite FTS5 keyword search without cloud access or telemetry.31 npm14MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI agents with persistent, local, and shareable project memory by storing decisions and code context in a searchable SQLite index, supporting keyword and semantic search via MCP.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to share persistent project memory across sessions and worktrees through content-hash file summaries, symbol lookup, bounded reads, notes, handoffs, claims, and agent messaging.451 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to store and recall scoped project memories in a local SQLite store using semantic search and a linked entity graph shared across MCP clients. It also provides optional code navigation tools for finding definitions, outlining files, listing imports, and comparing symbols between Git revisions.123 npm9MIT
- AlicenseBqualityDmaintenanceProvides local, explicitly scoped memory for coding agents via MCP, storing durable project knowledge in a per-repository SQLite database with tools to record, search, and retrieve context.5MIT
TDQS
Scored across 4 tools
The four tools target distinct phases: search (summary list), read (full content by ID), save (new record), and link (relations between records). The only minor overlap is that save_memory can optionally create relations via relates_to, which slightly blurs with link_memory, but the descriptions clarify the intended usage.
All tools use snake_case with a consistent verb_noun pattern: search_memory, read_raw_data, save_memory, link_memory. 'read_raw_data' is slightly less consistent than a hypothetical 'read_memory', but the overall convention is clear and predictable.
With 4 tools, the server provides a focused, non-redundant set that covers the core memory operations. This is well within the ideal range, and each tool has a clear, distinct purpose.
The set covers create, read, search, and link, but lacks update and delete operations for existing memories. While the supersedes relation may mitigate some needs, there is no direct way to modify or remove a record, which is a notable gap.