marketnow-memory
Related Servers
Alternatives to marketnow-memory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.28 npmMIT
- AlicenseAqualityDmaintenanceProvides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.12MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and any MCP-compatible client to persist, search, update, and delete plain-text memories across sessions, using BM25 lexical ranking over SQLite FTS5 with namespace filtering, tags, free-form metadata, and JSONL export/import — entirely local, with zero external infrastructure.1MIT
- AlicenseNot gradedqualityAmaintenanceProvides persistent memory for AI coding agents via MCP, enabling agents to store and semantically recall facts, events, and lessons across sessions, all running locally without cloud dependencies.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides local-first persistent memory with a typed knowledge graph and bounded multi-hop retrieval via MCP, letting coding agents and local LLM systems store, search, and recall facts across sessions without hosted services or model dependencies.MIT
- AlicenseNot gradedqualityCmaintenanceProvides a local-first persistent memory layer for AI coding agents through MCP, enabling them to save, search, retrieve, update, and consolidate project context, technical decisions, debugging solutions, and developer preferences across sessions.MIT
TDQS
Scored across 8 tools
Each tool targets a distinct memory operation: bootstrap, search, add, profile, clear, forget, status, and export. Even memory_bootstrap and memory_search are clearly separated by purpose and description.
All tools follow a consistent memory_<action> pattern, making the tool set predictable and easy to navigate. The two noun-like names (profile, status) still read as actions in context and do not break the pattern.
Eight tools is well-scoped for a memory service, covering retrieval, storage, deletion, inspection, export, and health checks without redundancy. Each tool earns its place.
The core memory lifecycle is covered: add, search, forget, clear, profile, export, and bootstrap. Minor gaps exist around updating an existing memory in place and importing memories back after export, but these can be worked around.