A
licenseNot graded
qualityA
maintenanceGives AI coding assistants persistent project memory and semantic code search, running fully locally with no API keys required.
MIT
aivectormemory
Related Servers
Alternatives to aivectormemory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides persistent long-term memory (semantic RAG) for AI coding assistants, enabling them to store and semantically search code and documentation across chat sessions without token limits.5MIT
Xanther memory Engineofficial
AlicenseNot gradedqualityBmaintenancePersistent memory for AI coding assistants.3MIT- FlicenseNot gradedqualityDmaintenanceProvides persistent memory and semantic file discovery for AI coding agents, enabling them to remember changes and find relevant files across sessions.5-
- AlicenseNot gradedqualityBmaintenanceProvides a local long-term memory layer for AI coding tools like Cursor and Claude Code, enabling cross-session, cross-tool sharing of project facts, user preferences, decisions, and workflows.36 npm2MIT
- AlicenseNot gradedqualityAmaintenanceProvides AI coding agents with a persistent memory layer to save, recall, update, and track memories across sessions and repositories using hybrid semantic search.4MIT
TDQS
B3.4/5.0
Scored across 8 tools
Disambiguation4/5
remember/recall/forget form a clean memory CRUD triad, and track/task/readme are distinct. However, auto_save ("save user preferences") overlaps conceptually with remember, which already supports user-level storage, creating a potential confusion point.
Naming Consistency3/5
Memory tools use verbs (remember, recall, forget) while track, task, status, and readme are bare nouns, and auto_save uses verb_noun. The convention is mixed but each name is still readable and guessable.
Tool Count4/5
Eight tools is a well-scoped set for a memory/session/task server, especially since track and task bundle multiple sub-actions internally. Slightly on the lean side but each tool earns its place.
Completeness4/5
Covers memory lifecycle (remember/recall/forget), session state, issue tracking, task management, and readme generation. Minor gaps like listing/exporting all memories or explicit memory update exist, but remember's auto-dedupe mitigates this.
Maintenance
ActivityInactive
ResponsivenessNo issues