flashmind
Related Servers
Alternatives to flashmind
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides 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.6 npm2MIT
- FlicenseNot gradedqualityAmaintenanceProvides AI coding agents with a local-first persistent memory layer they can read and write during sessions, storing decisions, preferences, error patterns, and research per project or globally. Enables semantic and keyword search, formatted context recall, and cross-project guideline surfacing without API keys or cloud storage.-
- FlicenseNot gradedqualityAmaintenanceGives AI coding agents a local-first persistent memory they can read and write directly during sessions, storing decisions, preferences, error patterns, and guidelines in per-project and global SQLite stores. Enables semantic and keyword retrieval of relevant context across sessions so agents start work already knowing a codebase's conventions and history.-
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.0Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read and write persistent memory directly during sessions, storing decisions, preferences, error patterns, research, and cross-project guidelines in local SQLite databases. Supports semantic search so relevant project and global context can be recalled by meaning, fully offline and without API keys.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to store decisions, preferences, and lessons in a local SQLite store, then recall the most relevant ones on demand. Runs fully local — no cloud, API keys, or per-query cost — and also exposes forget and consolidate operations.2Apache 2.0
TDQS
Scored across 8 tools
The tools are mostly distinct: save, get, list, update, delete form clear CRUD roles, while context/search/verify have explicit usage guidance. There is some overlap between search, list, context, and verify since all retrieve candidate memories, but the descriptions give enough cues to choose correctly.
All tools use a consistent memory_ prefix followed by a clear verb or noun, in uniform snake_case. The pattern is predictable across the entire set.
Eight tools is well-scoped for a memory service: CRUD operations plus search, list, context digest, and verification. No tool feels redundant or missing at the count level.
The surface covers the full memory lifecycle: create/save, read (get/list/search/context), update, delete, and verification. No obvious operational gaps for the stated purpose.