wanyi
Related Servers
Alternatives to wanyi
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.2,052 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to automatically capture durable knowledge and retrieve only relevant, token-bounded context from a secure local-first long-term memory, with support for progressive disclosure, snapshots, health diagnostics, and background tasks.-

slowaveofficial
AlicenseAqualityAmaintenanceProvides a local, adaptive memory layer that lets AI agents persist and retrieve decisions, constraints, and lessons across sessions without requiring an LLM API key.511AGPL 3.0- AlicenseAqualityAmaintenanceGives AI agents persistent, local-first memory using SQLite and on-device embeddings, enabling semantic search and recall across sessions with no cloud calls.87MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store, recall, update, delete, and analyze persistent memories with semantic search, decay, and anomaly retrieval across hosted, self-hosted, or fully local storage modes.53 npm22MIT
- FlicenseNot gradedqualityCmaintenanceProvides AI agents with persistent, local cross-session shared memory by combining vector semantic retrieval with knowledge graph relationships, and supports short/long-term memory management and local backups.-
TDQS
Scored across 23 tools
Most tools target a distinct memory lifecycle or guardrail function, and the detailed descriptions help separate recall from graph search, consolidation from deep gardening, and the various moat tools. A few pairs (LOAD hook vs. proactive partner's brief, sleep consolidation vs. gardener) could still be confused at first glance.
All tools share the consistent 万忆 prefix, but the second element mixes noun-style names like 错题本 and 园艺师 with verb-object names like 记录见闻 and 更新交易锚点. The naming is readable, but there is no uniform verb_noun convention across the set.
With 23 tools, this sits in the heavy range, and many tools bundle multiple subcommands, making the actual surface even larger. The count is not absurd for a comprehensive memory-and-reflection system, but it feels over-scoped for a typical MCP server.
The server covers memory writing, recall, compression, consolidation, self-checks, hooks, progress persistence, and proactive guardrails very extensively. However, there is no explicit general memory update or delete/forget tool, which leaves a notable gap in the core CRUD lifecycle for arbitrary memories.